All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] support: move patch-kernel.sh and rename it
Date: Mon, 19 Sep 2011 14:27:08 +0200	[thread overview]
Message-ID: <4E77351C.6000302@atmel.com> (raw)
In-Reply-To: <20110917063643.361CC8D728@busybox.osuosl.org>

Hello,

On 9/17/2011 8:22 AM, Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=59a326b934737483531c49c99acda7874c72e335
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> The name "patch-kernel.sh" is a bit stupid, since this script is used
> to patch everything in Buildroot, not only kernel trees.
By the way, what do you think about a old patch ([RFC PATCH 
v2]kernel-patch.sh: script changed to support archives in a proper way) 
I have sent since I had troubles to apply several patches (contained 
into a compressed archive) to the kernel because the order to apply 
patch was not correct.

Does BuildRoot offer another way to manage this case and I have missed it ?


> Signed-off-by: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
> Signed-off-by: Peter Korsgaard<jacmet@sunsite.dk>
>
Regards

Ludovic

  parent reply	other threads:[~2011-09-19 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17  6:22 [Buildroot] [git commit] support: move patch-kernel.sh and rename it Peter Korsgaard
2011-09-19  7:44 ` Sven Neumann
2011-09-19  8:14   ` Peter Korsgaard
2011-09-19 12:27 ` Ludovic Desroches [this message]
2011-09-19 20:47   ` Thomas Petazzoni
2011-09-20 10:04     ` Ludovic Desroches
2011-09-20 12:01       ` Thomas Petazzoni

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=4E77351C.6000302@atmel.com \
    --to=ludovic.desroches@atmel.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 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.