From: Jakub Narebski <jnareb@gmail.com>
To: David <wizzardx@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: User's mailing list? And multiple cherry pick
Date: Wed, 04 Jun 2008 01:05:07 -0700 (PDT) [thread overview]
Message-ID: <m3mym1zkus.fsf@localhost.localdomain> (raw)
In-Reply-To: <18c1e6480806040013l72da09aem30f91183e4fcbe41@mail.gmail.com>
David <wizzardx@gmail.com> writes:
[Please don't remove quote attributions]
>>> for C in $(git log --reverse <commit1>..<commit2> --pretty=format:%H);
>>> do git-cherry-pick $C; done
>>>
>>> Is there an easier syntax for doing this?
>>
>> rebase --onto?
>>
>
> Thanks, I checked the manuals further, and it looks like this will
> (mostly) do what I need.
>
> What's still missing is multiple cherry pick ;-)
>
> In other words, is there a simple way to *copy* a large number of
> commits from one branch to another, without rebasing?
# make temporary branch to not move to-be-copied during rebase
$ git checkout -b tmp-rebase to-be-copied
# copy commits; results are in just created temporary branch
$ git rebase --onto branch copy-from tmp-rebase
# check if everything is all right and rename temporary branch
# to final name
$ git branch -M tmp-rebase branch
That said, cherry-picking multiple commits is often requested feature.
I guess that git-sequencer GSoC 2008 project would help in having it
finally implemented. BTW. why can't you use topic branches and
merging?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-06-04 8:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 6:55 User's mailing list? And multiple cherry pick David
2008-06-04 6:58 ` Junio C Hamano
2008-06-04 7:13 ` David
2008-06-04 8:05 ` Jakub Narebski [this message]
2008-06-04 8:23 ` Johan Herland
2008-06-04 8:30 ` David
2008-06-04 9:39 ` Wincent Colaiuta
2008-06-04 10:02 ` David
2008-06-04 11:02 ` Wincent Colaiuta
2008-06-04 11:09 ` Jakub Narebski
2008-06-04 18:09 ` Björn Steinbrink
2008-06-04 8:16 ` Johan Herland
2008-06-04 7:39 ` Jakub Narebski
2008-06-04 8:11 ` David
2008-06-04 8:50 ` Jakub Narebski
2008-06-04 9:37 ` David
2008-06-04 9:47 ` Jakub Narebski
2008-06-04 11:36 ` Theodore Tso
2008-06-04 10:38 ` Karl Hasselström
2008-06-04 11:10 ` Miklos Vajna
2008-06-04 8:00 ` Stephan Beyer
2008-06-04 8:20 ` David
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=m3mym1zkus.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=wizzardx@gmail.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).