From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [PATCHv2 0/3] u-boot recipe updates
Date: Mon, 09 Jul 2012 20:08:25 +0100 [thread overview]
Message-ID: <1341860905.22321.1.camel@ted> (raw)
In-Reply-To: <1341849720.20265.64.camel@phil-desktop>
On Mon, 2012-07-09 at 17:01 +0100, Phil Blundell wrote:
> On Thu, 2012-07-05 at 12:14 -0400, Paul Gortmaker wrote:
> > > On Wed, 2012-07-04 at 11:00 -0400, Paul Gortmaker wrote:
> > > > > On a related note, is it possible to fix the mailing list so that it
> > > > > does not strip To/Cc information and Message-ID strings? [I'd have to
> > > > > check -- maybe it is (also) inserting a needless Reply-To: header that
> > > > > messes things up.]
> >
> > Your mail suffers the exact same problem. My address is nowhere to be
> > seen on the To/Cc: I only happened to see it since I told mutt to
> > show me all archived poky/oe mails with u-boot in the subject.
> > Otherwise your message would have been lost in the noise, perhaps seen
> > next week when I return from OOO.
> >
> > And when I hit reply, it won't go to you unless I tell mutt to ignore
> > the broken Reply-To line. It is the line right at the bottom:
>
> Ah, I see. So, just to be clear, the mailing list isn't stripping
> anything: the reason that your address doesn't appear in To/Cc is, as
> you suggest, purely because the Reply-to: header which mailman inserts
> tends to cause replies to be sent only to the list.
>
> I tend to agree with you that the Reply-to header is a bad idea and it
> would be better off disabled, but this is a list policy decision and
> Richard, as the administrator, would need to decide whether he wants to
> disable it or not.
I'm fairly indifferent about this and happy to change it unless anyone
can think of a good reason why its list this. I would note that whilst
in theory I might admin the list, I don't have any of the list admin
password for this list or the tsc one for that matter, only that for
bitbake-devel. Phil, perhaps we could discuss this offline :)
Cheers,
Richard
next prev parent reply other threads:[~2012-07-09 19:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 18:35 [PATCH 0/3] u-boot recipe updates Paul Gortmaker
2012-06-29 18:35 ` [PATCH 1/3] u-boot: Don't make the -Os removal part of global settings Paul Gortmaker
2012-06-29 21:55 ` Khem Raj
2012-06-29 22:01 ` Wolfgang Denk
2012-06-29 22:11 ` Khem Raj
2012-06-29 23:34 ` Wolfgang Denk
2012-06-30 2:49 ` Khem Raj
2012-07-01 22:03 ` Saul Wold
2012-07-01 23:14 ` Khem Raj
2012-07-02 3:04 ` Paul Gortmaker
2012-07-02 5:44 ` [PATCHv2 0/3] u-boot recipe updates Paul Gortmaker
2012-07-02 5:44 ` [PATCHv2 1/3] u-boot: Don't make the -Os removal part of global settings Paul Gortmaker
2012-07-02 11:23 ` Otavio Salvador
2012-07-02 5:44 ` [PATCHv2 2/3] u-boot: make FILESDIR a shared setting Paul Gortmaker
2012-07-02 11:24 ` Otavio Salvador
2012-07-02 13:33 ` Chris Larson
2012-07-02 16:42 ` Otavio Salvador
2012-07-02 19:03 ` Richard Purdie
2012-07-02 5:44 ` [PATCHv2 3/3] u-boot: do not clobber PARALLEL_MAKE setting Paul Gortmaker
2012-07-02 11:25 ` Otavio Salvador
2012-07-03 17:48 ` [PATCHv2 0/3] u-boot recipe updates Saul Wold
2012-07-04 14:12 ` Paul Gortmaker
2012-07-04 15:00 ` Paul Gortmaker
2012-07-04 15:29 ` Phil Blundell
2012-07-05 16:14 ` Paul Gortmaker
2012-07-09 16:01 ` Phil Blundell
2012-07-09 18:20 ` McClintock Matthew-B29882
2012-07-09 18:52 ` Paul Gortmaker
2012-07-09 19:08 ` Richard Purdie [this message]
2012-07-04 15:23 ` [PATCH] u-boot: make FILESDIR a shared setting via FILESPATH Paul Gortmaker
2012-07-04 15:38 ` Martin Jansa
2012-07-04 17:01 ` Richard Purdie
2012-07-05 17:19 ` Saul Wold
2012-06-29 18:35 ` [PATCH 2/3] u-boot: make FILESDIR a shared setting Paul Gortmaker
2012-06-29 18:35 ` [PATCH 3/3] u-boot: make sure CROSS_COMPILE is passed into build Paul Gortmaker
2012-06-29 20:04 ` McClintock Matthew-B29882
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=1341860905.22321.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.org \
/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.