Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] manual: update for multiple global patch dirs
Date: Tue, 17 Dec 2013 16:43:37 +0100	[thread overview]
Message-ID: <52B07129.8000900@mind.be> (raw)
In-Reply-To: <20131217160207.3ddd3a69@skate>

On 17/12/13 16:02, Thomas Petazzoni wrote:
> Dear Ryan Barnett,
>
> On Tue, 17 Dec 2013 08:24:47 -0600, Ryan Barnett wrote:
>
>> I was going to follow-up this patch with another series that removes
>> the options PATCH_DIR options for individual packages besides the
>> kernel. When I do that, I was planning on cleaning up the
>> documentation to avoid this duplication. It was easier for right now,
>> to duplicate the section Arnout requested rather than to try to
>> figure out the best way possible for avoiding duplication.
>
> Hmm, for which packages do you want to remove the PATCH_DIR options? If
> they exist for some packages, it's quite hard to remove them, as you're
> breaking compatibility. Not sure what should be our backward
> compatibility guarantee in this kind of cases.
>
> And why "besides the kernel" ?

  Read the rest of the thread :-)

  In summary:

- For U-Boot, Barebox, maybe others there are config options which 
provide exactly the same functionality as GLOBAL_PATCH_DIR. So these 
options can be removed IMHO (with Config.in.legacy pointing to the 
GLOBAL_PATCH_DIR option).

- For the kernel, there is an option that provides a slightly different 
functionality: it allows to download patches in addition to using patches 
on the local system.


  Regards,
  Arnout


-- 
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

  reply	other threads:[~2013-12-17 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  9:00 [Buildroot] [PATCH v4 1/2] Support for multiple BR2_GLOBAL_PATCH_DIR Ryan Barnett
2013-12-17  9:00 ` [Buildroot] [PATCH v4 2/2] manual: update for multiple global patch dirs Ryan Barnett
2013-12-17 12:58   ` Thomas De Schampheleire
2013-12-17 13:19     ` Arnout Vandecappelle
2013-12-17 13:30       ` Thomas De Schampheleire
2013-12-17 14:31         ` Arnout Vandecappelle
2013-12-17 14:24       ` Ryan Barnett
2013-12-17 15:02         ` Thomas Petazzoni
2013-12-17 15:43           ` Arnout Vandecappelle [this message]
2013-12-17 16:07         ` Thomas De Schampheleire
2013-12-17 16:09           ` Thomas De Schampheleire
2013-12-17 16:30           ` Ryan Barnett
2013-12-17 12:46 ` [Buildroot] [PATCH v4 1/2] Support for multiple BR2_GLOBAL_PATCH_DIR Thomas De Schampheleire

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=52B07129.8000900@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