From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [CONSOLIDATED PULL 0/4] 10-June
Date: Fri, 10 Jun 2011 17:33:26 +0100 [thread overview]
Message-ID: <1307723606.15712.213.camel@rex> (raw)
In-Reply-To: <cover.1307686598.git.sgw@linux.intel.com>
On Thu, 2011-06-09 at 23:26 -0700, Saul Wold wrote:
> Kang Kai (1):
> ghostscript: update SRC_URI
>
> Nitin A Kamble (1):
> gcc: rebase the patch to avoid patch rejection
This was a disaster. It breaks the build and is huge, thereby clogging
up the source control system web interface etc.
I applied it, then had to revert it. Please test things like this more
carefully in future.
I also think we need to put these kind of patches on the website or in a
repo, we shouldn't be carrying them around in the main repo.
> Phil Blundell (1):
> busybox: backport distro-features handling from oe master
>
> Saul Wold (1):
> multiple recipes converted to -staticdev packages
I'm with Phil on this one, needs more work.
I haven't got to the other two since the gcc issue distracted me :/.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-10 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 6:26 [CONSOLIDATED PULL 0/4] 10-June Saul Wold
2011-06-10 6:26 ` [CONSOLIDATED PULL 1/4] ghostscript: update SRC_URI Saul Wold
2011-06-10 6:26 ` [CONSOLIDATED PULL 2/4] busybox: backport distro-features handling from oe master Saul Wold
2011-06-10 6:26 ` [CONSOLIDATED PULL 3/4] gcc: rebase the patch to avoid patch rejection Saul Wold
2011-06-10 6:26 ` [CONSOLIDATED PULL 4/4] multiple recipes converted to -staticdev packages Saul Wold
2011-06-10 9:25 ` Phil Blundell
2011-06-10 9:43 ` Phil Blundell
2011-06-10 18:36 ` Saul Wold
2011-06-10 21:36 ` Phil Blundell
2011-06-10 22:46 ` Saul Wold
2011-06-10 22:04 ` Khem Raj
2011-06-10 16:33 ` Richard Purdie [this message]
2011-06-10 16:54 ` [CONSOLIDATED PULL 0/4] 10-June Saul Wold
2011-06-10 16:59 ` Koen Kooi
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=1307723606.15712.213.camel@rex \
--to=richard.purdie@linuxfoundation.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.