Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 4/6] apply-patches.sh: directories are considered as a collection of patches
Date: Thu, 16 Feb 2012 10:45:10 +0100	[thread overview]
Message-ID: <201202161045.11127.arnout@mind.be> (raw)
In-Reply-To: <20120216084953.GB2943@ldesroches-Latitude-E6320>

On Thursday 16 February 2012 09:49:53 Ludovic Desroches wrote:
> I mean I don't know which parameters will be passed to apply-patches but I
> worry about having package/foo/ (with some version directories into it) as
> parameter and then explore and apply all the patches contained into this tree.

 I don't think that's an issue, because apply-patches will be called with 
*.patch as a pattern - the version-specific directories will not be called
*.patch.


> I would like to keep it because I was thinking of debian-patches like: a
> structure with several directories where we may find some patches. From the
> top of my head I think it's not the case for debian-patches because patches
> are located at the root level but I presume that we could face this kind of
> patch.

 If you don't have a concrete use case, I would leave this feature out.
Otherwise you don't even know if it does work in practice.  We can always
add the feature again later if it turns out to be required.

 ThomasDS (in CC) has a use case of a tar file containing patches.  Maybe
he has a concrete use case.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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:[~2012-02-16  9:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  1:47 [Buildroot] [RFC PATCH]apply-patches.sh: big update (new directory and archive management) ludovic.desroches at atmel.com
2012-02-06  1:47 ` [Buildroot] [RFC PATCH 1/6] apply-patches.sh: check if there are rejects before applying patches ludovic.desroches at atmel.com
2012-02-10 21:43   ` Arnout Vandecappelle
2012-02-15 16:55     ` Ludovic Desroches
2012-02-15 22:33       ` [Buildroot] [RFC PATCH v2 " ludovic.desroches at atmel.com
2012-02-15 20:56         ` Arnout Vandecappelle
2012-02-06  1:47 ` [Buildroot] [RFC PATCH 2/6] apply-patches.sh: rename targetdir to builddir ludovic.desroches at atmel.com
2012-02-10 21:45   ` Arnout Vandecappelle
2012-02-06  1:47 ` [Buildroot] [RFC PATCH 3/6] apply-patches.sh: cleanup ludovic.desroches at atmel.com
2012-02-10 21:45   ` Arnout Vandecappelle
2012-02-06  1:47 ` [Buildroot] [RFC PATCH 4/6] apply-patches.sh: directories are considered as a collection of patches ludovic.desroches at atmel.com
2012-02-10 22:40   ` Arnout Vandecappelle
2012-02-15 16:51     ` Ludovic Desroches
2012-02-15 23:06       ` [Buildroot] [RFC PATCH v2 " ludovic.desroches at atmel.com
2012-02-15 23:49         ` Arnout Vandecappelle
2012-02-16  7:56           ` Ludovic Desroches
2012-02-16  8:49       ` [Buildroot] [RFC PATCH " Ludovic Desroches
2012-02-16  9:45         ` Arnout Vandecappelle [this message]
2012-02-06  1:47 ` [Buildroot] [RFC PATCH 5/6] apply-patches.sh: add recursivity when scanning patchdir ludovic.desroches at atmel.com
2012-02-06  1:47 ` [Buildroot] [RFC PATCH 6/6] apply-patches.sh: change archive management ludovic.desroches at atmel.com
2012-02-10 22:48   ` Arnout Vandecappelle
2012-02-15 16:54     ` Ludovic Desroches
2012-02-15 23:09       ` [Buildroot] [RFC PATCH v2 " ludovic.desroches at atmel.com
2012-02-15 23:54         ` Arnout Vandecappelle

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=201202161045.11127.arnout@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