From: JS <js@hipro.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] reply-to munging (was) [Fwd: Re: svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86]
Date: Sat, 22 Mar 2008 00:08:28 +0530 [thread overview]
Message-ID: <1206124708.4692.6.camel@localhost> (raw)
In-Reply-To: <1206120659.2562.111.camel@nigel-x60>
On Fri, 2008-03-21 at 17:30 +0000, Nigel Kukard wrote:
> Argh ... would it be ok to set the default ML reply-to as the ML? or an
> insane proposition from my side? ;)
Is 'reply-to munging' against list policy?
--
HiPro Solutions
http://hipro.co.in/
prev parent reply other threads:[~2008-03-21 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 17:30 [Buildroot] [Fwd: Re: svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86] Nigel Kukard
2008-03-21 18:38 ` JS [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206124708.4692.6.camel@localhost \
--to=js@hipro.co.in \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.