From: Felipe Contreras <felipe.contreras@gmail.com>
To: me@felipebalbi.com
Cc: git@vger.kernel.org
Subject: Re: cherry picking several patches at once
Date: Sat, 23 Jan 2010 01:57:40 +0200 [thread overview]
Message-ID: <94a0d4531001221557n7a892f03u5e5d1c5e5ba5fea0@mail.gmail.com> (raw)
In-Reply-To: <20100121161157.GA3628@gandalf>
Heippa,
On Thu, Jan 21, 2010 at 6:11 PM, Felipe Balbi <me@felipebalbi.com> wrote:
> I wonder if it's possible to cherry several patches at once ?
> Can't find anything on any docs, but something like:
>
> $ git cherry-pick <commit_id_start>..<commit_id_end> -- \
> /path/to/directory
>
> I want to do that because I keep patches to the musb driver (on linux
> kernel) based on top of linus' mainline tree and on top of internal
> tree.
>
> The internal tree is outdated (not following mainline), but the musb
> driver is basically in sync, so cherry picking works, but it's a bit
> painful when I have to pick patches from community and manually
> cherry-pick to the other branch based on my internal tree.
>
> If there's a way (besides git rebase --onto) to do that I would very
> much like to know.
Have you tried something like:
git format-patch old-base --full-diff -- /path
git am -3 *.patch
> Another thing that would be nice to have, is to pass the HEAD to which
> we want to cherry-pick, so we can cherry-pick to not-checked-out
> branches.
I think that would not be possible because of the challenges when
dealing with conflicts.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2010-01-23 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:11 cherry picking several patches at once Felipe Balbi
2010-01-22 23:57 ` Felipe Contreras [this message]
2010-01-23 0:24 ` Marc Weber
2010-01-23 11:17 ` Sverre Rabbelier
2010-01-24 10:52 ` Felipe Balbi
2010-01-24 13:10 ` Felipe Contreras
2010-01-24 15:31 ` Marc Weber
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=94a0d4531001221557n7a892f03u5e5d1c5e5ba5fea0@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@felipebalbi.com \
/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;
as well as URLs for NNTP newsgroup(s).