From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 0/1] A script to clean obsolete sstate cache files
Date: Wed, 22 Feb 2012 16:09:37 +0000 [thread overview]
Message-ID: <1329926977.20261.168.camel@ted> (raw)
In-Reply-To: <CAP9ODKo_94H_HkxHbvpe-hXpS6t0=5Dqv5QUSHPW+DsYJ=jncA@mail.gmail.com>
On Wed, 2012-02-22 at 13:56 -0200, Otavio Salvador wrote:
> On Wed, Feb 22, 2012 at 13:53, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > Except here we are talking about a single patch that adds a single file, which
> > is easily downloadable from the web interface. If it were more complicated I
> > could understand the fuss, but right now this is almost ridiculous.
>
> It doesn't seem that easy; it seems Koen tried to apply it and it has failed.
>
> Besides, Robert didn't complain about people asking it to be resend.
> Who is complaining is Richard and I am just justifying the reasoning
> why it is more the logical to expect it to be done based on OE-Core.
In this case, Richard is presenting the viewpoint he's heard expressed
by a number of people in private but who don't want to rock the boat on
the mailing list. I'd like to see the mailing list be a friendly place
where people don't get flamed for posting patches. Some of the recent
responses are less than friendly and I think its reasonable to try and
resolve this.
I'm going to propose that if trees are poky based, the pull request
should indicate this. People can then act accordingly. No indication
means its oe-core derived.
Cheers,
Richard
next prev parent reply other threads:[~2012-02-22 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 13:27 [PATCH 0/1] A script to clean obsolete sstate cache files Robert Yang
2012-02-22 13:27 ` [PATCH 1/1] " Robert Yang
2012-02-22 13:42 ` [PATCH 0/1] " Koen Kooi
2012-02-22 14:15 ` Richard Purdie
2012-02-22 14:32 ` Koen Kooi
2012-02-22 15:06 ` Richard Purdie
2012-02-22 15:11 ` Koen Kooi
2012-02-22 16:05 ` Richard Purdie
2012-02-22 16:08 ` Otavio Salvador
2012-02-22 15:47 ` Otavio Salvador
2012-02-22 15:53 ` Paul Eggleton
2012-02-22 15:56 ` Otavio Salvador
2012-02-22 16:09 ` Richard Purdie [this message]
2012-02-22 16:16 ` Otavio Salvador
2012-02-22 16:43 ` Richard Purdie
2012-02-22 16:00 ` Phil Blundell
2012-02-22 14:48 ` Otavio Salvador
2012-02-24 4:13 ` Saul Wold
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=1329926977.20261.168.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.