All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Larson <kergoth@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] patch.bbclass: abstract out logic that determines patches to apply
Date: Tue, 27 Dec 2011 10:31:31 -0700	[thread overview]
Message-ID: <CABcZAN=tn0f=xNFepSeOMT--yvPX-UKCj0fa-0WMeuWsAAro5Q@mail.gmail.com> (raw)
In-Reply-To: <1324488253.19860.4.camel@ted>

On Wed, Dec 21, 2011 at 10:24 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Tue, 2011-12-20 at 10:38 -0700, Christopher Larson wrote:
>> This is needed by the copyleft_compliance class, so it can emit series files
>> for the patches, which greatly increases their usefulness to a user
>> trying to
>> reconstruct the sources outside of OE.
>>
>> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
>> ---
>>   meta/classes/patch.bbclass |  196
>> +++++++++++++++++++++++--------------------
>>   1 files changed, 105 insertions(+), 91 deletions(-)
>
> I have no objection to the change but the patch seems to be mangled
> somehow. Could you resend it or point me at a git tree please?

Sorry about that, my git send-email isn't working on my main dev
machine at the moment, strange error from git that no one seems to
recognize. used imap-send, and apparently tbird defaults to wrapping
the same way the gmail UI does *eyeroll*. See
https://github.com/kergoth/oe-core/compare/patch-refactor
-- 
Christopher Larson



  reply	other threads:[~2011-12-27 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 17:38 [PATCH] patch.bbclass: abstract out logic that determines patches to apply Christopher Larson
2011-12-20 18:28 ` Bruce Ashfield
2011-12-21 17:24 ` Richard Purdie
2011-12-27 17:31   ` Chris Larson [this message]
2011-12-27 20:33 ` Saul Wold
2011-12-27 20:38   ` Chris Larson
2011-12-28  3:18     ` Christopher Larson
2012-01-03 23:52       ` 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='CABcZAN=tn0f=xNFepSeOMT--yvPX-UKCj0fa-0WMeuWsAAro5Q@mail.gmail.com' \
    --to=kergoth@gmail.com \
    --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.