threads / discuss / 20903

one half of a rebase

Subject: one half of a rebase

## tl;dr

5 messages between Sep 11, 2009 and Sep 12, 2009.

replies: 4people: 4as markdown or json

Geoffrey Irving· Sep 11, 2009, 17:25 UTC · lore
If I'm on branch topic and do "git rebase master", git performs two operations:
1. Rewind the current head to master.
2. For each commit in topic that isn't in master, cherry pick it onto
the current head.

I would like to be able to do (2) as a separate operation. For example, if I start out on branch master and want to get all of topic's commits on top of the current head, I currently do

    git checkout topic
    git rebase master
    git branch -d master
    git branch -m master
If I could do (2) as a separate operation, it would look something like
    git cherry-pick-all topic

which is simpler and faster since it avoids switching files back and forth (master to topic and back). Is there a robust way to achieve the cherry-pick-all semantics with current commands? If not, how difficult would it be to partition rebase accordingly?

Thanks, Geoffrey

Matthieu Moy· Sep 11, 2009, 18:39 UTC · re: Geoffrey Irving · lore

Re: one half of a rebase

Geoffrey Irving <irving@naml.us> writes:
> If I could do (2) as a separate operation, it would look something like
>
>     git cherry-pick-all topic
I believe
  git rebase --onto master master topic
  git update-ref master topic
would do the trick.
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Alex Riesen· Sep 11, 2009, 21:10 UTC · re: Geoffrey Irving · lore

Re: one half of a rebase

On Fri, Sep 11, 2009 at 19:25, Geoffrey Irving <irving@naml.us> wrote:
Show 8 quoted lines
> If I could do (2) as a separate operation, it would look something like
>
>    git cherry-pick-all topic
>
> which is simpler and faster since it avoids switching files back and
> forth (master to topic and back).  Is there a robust way to achieve
> the cherry-pick-all semantics with current commands?  If not, how
> difficult would it be to partition rebase accordingly?
I have this in my .bashrc:
$ gcp3 ()
{
    git format-patch -k --stdout --full-index "$@" | git am -k -3 --binary
}
Then, while on master branch:
$ gcp3 master..topic
Geoffrey Irving· Sep 12, 2009, 02:23 UTC · re: Alex Riesen · lore

Re: one half of a rebase

On Fri, Sep 11, 2009 at 5:10 PM, Alex Riesen<raa.lkml@gmail.com> wrote:
Show 20 quoted lines
> On Fri, Sep 11, 2009 at 19:25, Geoffrey Irving <irving@naml.us> wrote:
>> If I could do (2) as a separate operation, it would look something like
>>
>>    git cherry-pick-all topic
>>
>> which is simpler and faster since it avoids switching files back and
>> forth (master to topic and back).  Is there a robust way to achieve
>> the cherry-pick-all semantics with current commands?  If not, how
>> difficult would it be to partition rebase accordingly?
>
> I have this in my .bashrc:
>
> $ gcp3 ()
> {
>    git format-patch -k --stdout --full-index "$@" | git am -k -3 --binary
> }
>
> Then, while on master branch:
>
> $ gcp3 master..topic
Great!  That should work nicely.
Geoffrey
Paolo Bonzini· Sep 12, 2009, 14:38 UTC · re: Geoffrey Irving · lore

Re: one half of a rebase

On 09/12/2009 04:23 AM, Geoffrey Irving wrote:
Show 10 quoted lines
> On Fri, Sep 11, 2009 at 5:10 PM, Alex Riesen<raa.lkml@gmail.com>  wrote:
>> On Fri, Sep 11, 2009 at 19:25, Geoffrey Irving<irving@naml.us>  wrote:
>>> If I could do (2) as a separate operation, it would look something like
>>>
>>>     git cherry-pick-all topic
>>>
>>> which is simpler and faster since it avoids switching files back and
>>> forth (master to topic and back).  Is there a robust way to achieve
>>> the cherry-pick-all semantics with current commands?  If not, how
>>> difficult would it be to partition rebase accordingly?

As mentioned by Alex "git am -3" is basically parsing + the second part of rebase. So, based on Alex's recipe, here is a possible alias for cherry-pick-all:

[alias]
	cherry-pick-all = "!f() { git format-patch -k --stdout --full-index 
`git symbolic-ref HEAD`..$1 | git am -k -3 --binary; }; f"

More useful (just because it is more generic) than "the second part of git rebase", a "sequencer" would be "the second part of git rebase -i", applying a custom script coming from stdin. If that was present, git cherry-pick-all could be done like this:

git log --pretty=tformat:'pick %h' master..topic | git sequencer

And here is yet another alternative, that however would only work only if the patches applies perfectly:

git log --pretty=format:%h master..topic | xargs -rn1 git cherry-pick
Paolo

← back to recent threads