Re: [PATCH 2/4] revisions passed to cherry-pick should be in "default" order
- From
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
- Date
- Aug 13, 2012, 20:10 UTC
- Message-ID
- <CAOeW2eENsnrPqBL795FcwMgHURS6YsPBW6FYvb=DwD-UtgPZ5g@mail.gmail.com>
- In-Reply-To
- <50289e50.a19f320a.5d99.3fdfSMTPIN_ADDED@gmr-mx.google.com>
On Sun, Aug 12, 2012 at 11:27 PM, <y@google.com> wrote:
Show 5 quoted lines
> From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
>
> 'git cherry-pick' internally sets the --reverse option while walking
> revisions, so that 'git cherry-pick branch@{u}..branch' will apply the
> revisions starting at the oldest one.By the way, I can see the usefulness of --reverse when giving a range, but I think it's a little confusing when not giving a range. So "git cherry-pick A B" will apply B first, then A. I thought I'd mention that explicitly in case it wasn't clear.