From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Chris Larson <chris_larson@mentor.com>
Subject: Re: [PATCH 1/2] Rename url params patch=<ignored>/pnum=<n> to apply={yes, no}/striplevel=<n>
Date: Mon, 24 May 2010 19:33:25 -0400 [thread overview]
Message-ID: <20100524233325.GJ25484@denix.org> (raw)
In-Reply-To: <1274733028-13432-1-git-send-email-clarson@kergoth.com>
On Mon, May 24, 2010 at 01:30:27PM -0700, Chris Larson wrote:
> From: Chris Larson <chris_larson@mentor.com>
>
> I think this makes the behavior rather more clear.
Ironically, just earlier today I was trying to explain to somebody, that
patch=3 does not mean or do anything...
It maybe more clear for new users, but once you use it couple times, it
doesn't matter if it's patch/pnum or apply/striplevel. But I see where you
going with the second patch.
> Signed-off-by: Chris Larson <chris_larson@mentor.com>
Acked-by: Denys Dmytriyenko <denis@denix.org>
> diff --git a/classes/patch.bbclass b/classes/patch.bbclass
> index a739b20..6ef408f 100644
> --- a/classes/patch.bbclass
> +++ b/classes/patch.bbclass
next prev parent reply other threads:[~2010-05-24 23:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 20:30 [PATCH 1/2] Rename url params patch=<ignored>/pnum=<n> to apply={yes, no}/striplevel=<n> Chris Larson
2010-05-24 20:30 ` [PATCH 2/2] Make the do_patch apply=yes param implicit if extension is .diff/.patch Chris Larson
2010-05-24 23:34 ` Denys Dmytriyenko
2010-05-25 4:42 ` Khem Raj
2010-05-24 23:33 ` Denys Dmytriyenko [this message]
2010-05-25 4:42 ` [PATCH 1/2] Rename url params patch=<ignored>/pnum=<n> to apply={yes, no}/striplevel=<n> Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2010-06-04 12:52 Frans Meulenbroeks
2010-06-04 13:33 ` Koen Kooi
2010-06-04 14:07 ` Chris Larson
2010-06-04 17:31 ` Tom Rini
2010-06-04 18:14 ` Chris Larson
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=20100524233325.GJ25484@denix.org \
--to=denis@denix.org \
--cc=chris_larson@mentor.com \
--cc=openembedded-devel@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.