From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: Allow to specify a list of patches
Date: Tue, 15 Jul 2014 22:35:52 +0200 [thread overview]
Message-ID: <20140715223552.04987eb6@free-electrons.com> (raw)
In-Reply-To: <20140715201336.GE3351@free.fr>
Dear Yann E. MORIN,
On Tue, 15 Jul 2014 22:13:36 +0200, Yann E. MORIN wrote:
> The more I think about it, the more I find our policy to require
> PKG-prefixed patches to be really cumbersome, since the patches already
> are in a subdir named PKG/
Actually, me too. It prevents the output of "git format-patch" from
being directly used as patches.
> Of course, we're enforcing this naming scheme in BR2_GLOBAL_PATCH_DIR to
> be in sync with what we do for our bundled patches.
>
> But still, if patches were just named NNNN-title.patch, that would be as
> efficient at sorting the patches. The PKG- prefix is not really
> required, and indeed can cause some troubles with some use-cases, such
> as yours.
>
> Thomas, was there a specific reason we wanted the patches to be
> PKG-prefixed? If not, would it make sense to just accept patches without
> a PKG-prefix?
I honestly don't remember what was the reasoning behind that. Arnout
maybe?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-15 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 18:26 [Buildroot] [PATCH] u-boot: Allow to specify a list of patches Ezequiel Garcia
2014-07-15 18:53 ` Thomas Petazzoni
2014-07-15 19:49 ` Ezequiel García
2014-07-15 20:13 ` Yann E. MORIN
2014-07-15 20:35 ` Thomas Petazzoni [this message]
2014-07-16 5:21 ` Thomas De Schampheleire
2014-07-16 22:23 ` Arnout Vandecappelle
2014-07-17 4:52 ` Thomas De Schampheleire
2014-07-17 7:48 ` Arnout Vandecappelle
2014-07-17 17:23 ` Yann E. MORIN
2014-07-17 23:20 ` Arnout Vandecappelle
2014-07-21 19:55 ` Ezequiel García
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=20140715223552.04987eb6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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