Re: [PATCH 3/3] rebase: new convenient option to edit a single commit
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Mar 3, 2014, 20:28 UTC
- Message-ID
- <CAPig+cTn-YcWHsGRKUZWqACJ5ZspWoB+f4i7hNj09_4Ci6odiw@mail.gmail.com>
- In-Reply-To
- <1393728794-29566-4-git-send-email-pclouds@gmail.com>
On Sat, Mar 1, 2014 at 9:53 PM, Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote:
Show 8 quoted lines
> "git rebase -e XYZ" is basically the same as > > EDITOR="sed -i '1s/pick XYZ/edit XYZ/' $@" \ > git rebase -i XYZ^ > > In English, it prepares the todo list for you to edit only commit XYZ > to save your time. The time saving is only significant when you edit a > lot of commits separately.
Is it correct to single out only "edit" for special treatment? If allowing "edit" on the command-line, then shouldn't command-line "reword" also be supported? I, for one, often need to reword a commit message (or two or three); far more frequently than I need to edit a commit.
(This is a genuine question about perceived favoritism of "edit", as opposed to a request to further bloat the interface.)