public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: Linux OMAP Users <linux-omap@vger.kernel.org>
Subject: Re: Script for applying a set of patches from a folder
Date: Fri, 05 Jun 2009 07:38:03 -0700	[thread overview]
Message-ID: <8763fad9v8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <3284AAA8-73B9-4C4C-95FD-29BC92AFE5A8@mac.com> (Elvis Dowson's message of "Fri\, 05 Jun 2009 14\:55\:41 +0400")

Elvis Dowson <elvis.dowson@mac.com> writes:

> 	Does anyone have a script that will allow me to apply all the
> patches  that are contained in a folder, using the git apply command?
>
> I have hundreds of patches that I want to apply from the dss2 and pm
> branches to the linux-omap-2.6 branch, locally, to bring it upto date,
> to a known state before making specific patches for the overo
> platform.

Not sure exactly what you're trying to do here, but since the PM
branch probably makes up most of those patches, why do you need to
apply them?  Can't you just checkout the pm branch and add the other
patches on top?  e.g.

Create a test branch for your work in progress which is rooted at the
pm branch:

$ git checkout -b wip/test pm

Apply your other patches (dss2, etc.)

$ git am <patches>

Kevin

  parent reply	other threads:[~2009-06-05 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3284AAA8-73B9-4C4C-95FD-29BC92AFE5A8@mac.com>
2009-06-05 12:10 ` Script for applying a set of patches from a folder Felipe Balbi
2009-06-05 13:49 ` Jean Pihet
2009-06-05 14:06   ` Curran, Dominic
2009-06-05 14:38 ` Kevin Hilman [this message]
     [not found] <A3273B39-7050-4382-BFE7-A1416B45DA55@mac.com>
2009-06-05 19:22 ` Gadiyar, Anand

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=8763fad9v8.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=elvis.dowson@mac.com \
    --cc=linux-omap@vger.kernel.org \
    /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