From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] pkg-generick.mk: support for multiple patch dirs
Date: Thu, 12 Dec 2013 23:25:59 +0100 [thread overview]
Message-ID: <52AA37F7.9000908@mind.be> (raw)
In-Reply-To: <1386838290-10978-1-git-send-email-rjbarnet@rockwellcollins.com>
Hi Ryan,
Oops, looks like I replied to an old version of this patch - but my
comment still stands.
Your title "pkg-generick.mk" sounds a bit special :-)
When you post updated versions of a patch (series), could you add v2 to
it (recent git allows you to do that with the '-v2' argument to
send-email or format-patch, older versions need '--subject-prefix='PATCH
v2' ).
Regards,
Arnout
On 12/12/13 09:51, Ryan Barnett wrote:
> Adding support for specifying multiple directories in
> BR2_GLOBAL_PATCH_DIR. This will allow for a layered approach for the
> patching of a package.
>
> Signed-off-by: Ryan Barnett <rjbarnet@rockwellcollins.com>
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-12-12 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 8:51 [Buildroot] [PATCH 1/2] pkg-generick.mk: support for multiple patch dirs Ryan Barnett
2013-12-12 8:51 ` [Buildroot] [PATCH 2/2] manual: update for multiple global " Ryan Barnett
2013-12-12 22:25 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-11 17:58 [Buildroot] [PATCH 1/2] pkg-generick.mk: support for multiple " Ryan Barnett
2013-12-11 18:36 ` Thomas De Schampheleire
2013-12-12 22:11 ` Arnout Vandecappelle
2013-12-13 9:26 ` rjbarnet at rockwellcollins.com
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=52AA37F7.9000908@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox