Re: [PATCH] cherry-pick: allow to pick to unborn branches

Michael J Gruber writes: > Here and below, I'm mimicking/copying the behavior that we have right > now already. I asked myself the same question - rolling back to orphan > state shouldn't be that hard after all. But that would be a change in > behavior that - if

Re: [PATCH] cherry-pick: allow to pick to unborn branches

Junio C Hamano venit, vidit, dixit 06.06.2016 22:06: > Michael J Gruber writes: > >> Currently, cherry-pick allows tp pick single commits to an empty HEAD >> but not multiple commits. >> >> Allow the multiple commit case, too. >> >> Reported-by: Fabrizio Cucci

Re: [PATCH] cherry-pick: allow to pick to unborn branches

Michael J Gruber writes: > Currently, cherry-pick allows tp pick single commits to an empty HEAD > but not multiple commits. > > Allow the multiple commit case, too. > > Reported-by: Fabrizio Cucci > Signed-off-by: Michael J Gruber

Re: [PATCH] cherry-pick: allow to pick to unborn branches

On 06.06.16 15:23, Michael J Gruber wrote: > Currently, cherry-pick allows tp pick single commits to an empty HEAD Typo: ^^ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH] cherry-pick: allow to pick to unborn branches

Currently, cherry-pick allows tp pick single commits to an empty HEAD but not multiple commits. Allow the multiple commit case, too. Reported-by: Fabrizio Cucci Signed-off-by: Michael J Gruber --- sequencer.c | 11 ++- 1 file