This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Mail client advice [off-topic]


On Mon, 20 Oct 2003, Eric Botcazou wrote:
> Btw, is it my mail reader or do you not reply to the original message when
> posting the review? This is a bit confusing, both for threaded mail readers
> and for the mailing-list archives. I know you're not the only one but,
> contrary to a few others, your mail reader seems to have a sane 'reply'
> feature.

Perhaps the list may be able to give me some advice on the topic.  I'm
currently using pine as my mail client to send outgoing mail, but I use
a web browser (Netscape 7.1) to read the gcc lists from the archives,
at http://gcc.gnu.org/ml/gcc-patches.  And just to make things slightly
more complicated, I run the browser on my client machine, but ssh to the
firewall/mailserver that I use to run pine.

In this configuration, I'm able to respond to messages e-mailed to me
preserving the mailing list threading, but try as I might I've been
unable to "de novo" contribute to an existing thread or add references
to an e-mail.  I can work out the relevant "Message-Id"s by looking at
the raw-text version of the posting, but despite modifying my ~/.pinerc
and even tweaking the pine source code and recompiling, I've been unable
to find a way of adding the appropriate "In-Reply-To:" and "References:"
headers to my postings.


I appreciate this is less than ideal, so I've been looking at alternatives
and religiously adding the thread information to the message itself, i.e.
giving the URL of the message I'm responding to.


I appreciate this is off-topic, but does anyone have any recommendations
for how I should be doing this?  Is the recommended approach to really
subscribe to the lists, probably under an alias to avoid overwhelming my
current mailbox?  This would work for gcc-patches, but I only rarely post
to gcc, so I'm guessing there might be a better solution.

Many thanks in advance,

Roger
--


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]