----------------------------------------------------------------------------------
@MSGID: <1qgqwud.1qo1i9s1j1n0cnN%snipeco.2@gmail.com>
a9861e8d
@REPLY: <fVDKthnhfJ8657wgg@bongo-ra.co> 43cedb22
@REPLYADDR Sn!pe <snipeco.2@gmail.com>
@REPLYTO 2:5075/128 Sn!pe
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<1qgqwud.1qo1i9s1j1n0cnN%snipeco.2@gmail.com>
@RFC-References:
<87h6o63g31.fsf@nosuchdomain.example.com> <3607596852@f172.n1.z21.fsxnet> 1@dont-email.me>
1@dont-email.me> 2@dont-email.me> <fVDKthnhfJ8657wgg@bongo-ra.co>
@RFC-Reply-To: snipeco.1@gmail.com (Sn!pe)
@TZUTC: 0100
@PID: MacSOUP/2.8.6b1 (ed136d9b90) (Mac OS
10.13.6)
@TID: FIDOGATE-5.12-ge4e8b94
Spiros Bousbouras <
spibou@gmail.com> wrote:
[...]
> Finally (for comp.lang.c only) , I find even more annoying than the spam
> the fact that people don`t choose an appropriate Subject: for their posts.
> Naming a thread "bart again (UCX64)" is a poor choice anyway but it
> contains a long subthread on whether the closing brace of a function is
> reachable and whether a compiler should give a warning. It would certainly
> help if posts relevant to this reflected it in the Subject: .There was
> another recent very long thread ("C vs Haskell for XML parsing") which
> touched on a variety of topics including whether C should support named
> arguments for functions. Again it would have helped if the various posts had
> an appropriate Subject: line to reflect what the post is about instead of
> keeping the original Subject: of the thread.
>
At the risk of teaching Granny to suck eggs, the way to change the
Subject of a Usenet thread is like this:
New Subject (Was: Old Subject)
This will cause competent User Agents to automatically discard the
(Was: Old Subject) part of the header when following up but maintain
continuity of Subject in the thread list. I have changed the Subject of
this post as an example.
--
^?^. Sn!pe <
https://youtu.be/_kqytf31a8E>
My pet rock Gordon just is.
--- MacSOUP/2.8.6b1 (ed136d9b90) (Mac OS 10.13.6)
* Origin: Sn!peCo World Wide Wading Birds (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441