From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 0/3] u-boot recipe updates
Date: Wed, 04 Jul 2012 16:29:24 +0100 [thread overview]
Message-ID: <1341415765.20265.30.camel@phil-desktop> (raw)
In-Reply-To: <20120704150005.GD1817@windriver.com>
On Wed, 2012-07-04 at 11:00 -0400, Paul Gortmaker wrote:
> I've found Richard's comments [looking in OE archive and not poky
> helped] and will test what he proposed to replace FILESDIR. But I still
> think it extremely worthwhile if some fine tuning to the mailing list(s)
> can be done to address what I mentioned below.
Can you be more specific about what you think should be changed? If I
look at the message of yours that I'm replying to, it has:
Return-Path: <openembedded-core-bounces@lists.openembedded.org>
Received: from linuxtogo.org ([188.40.83.200]) by hetzner.pbcl.net with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <openembedded-core-bounces@lists.openembedded.org>) id 1SmR3u-0002an-JT for pb@pbcl.net; Wed, 04 Jul 2012 17:00:14 +0200
Received: from localhost ([127.0.0.1]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from <openembedded-core-bounces@lists.openembedded.org>) id 1SmREX-0006Iq-NQ; Wed, 04 Jul 2012 17:11:13 +0200
Received: from mail1.windriver.com ([147.11.146.13]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from <Paul.Gortmaker@windriver.com>) id 1SmREW-0006Ih-OQ for openembedded-core@lists.openembedded.org; Wed, 04 Jul 2012 17:11:13 +0200
[...]
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Message-id: <20120704150005.GD1817@windriver.com>
Cc: openembedded-core@lists.openembedded.org
which all seems in order. Which part do you think is wrong?
> > 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.]
> >
> > Further, without a proper Message-ID, it breaks patchworks, so Richard's
> > comments should be here:
p.
next prev parent reply other threads:[~2012-07-04 15:40 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 [this message]
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
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=1341415765.20265.30.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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.