Thread (4 messages) flat view 4 messages, 3 authors, 2016-12-10

Re: BUG: "cherry-pick A..B || git reset --hard OTHER"

From: Junio C Hamano <hidden>
Date: 2016-12-09 18:07:10

Duy Nguyen [off-list ref] writes:
On Thu, Dec 8, 2016 at 3:04 AM, Junio C Hamano [off-list ref] wrote:
quoted
Stephan Beyer [off-list ref] writes:
quoted
[1] By the way: git cherry-pick --quit, git rebase --forget ...
different wording for the same thing makes things unintuitive.
It is not too late to STOP "--forget" from getting added to "rebase"
and give it a better name.
Having the same operation with different names only increases git
reputation of bad/inconsistent UI. Either forget is renamed to quit,
or vice versa. I prefer forget, but the decision is yours and the
community's. So I'm sending two patches to rename in either direction.
You can pick one.
I actually was advocating to remove both by making --abort saner.
With an updated --abort that behaves saner, is "rebase --forget"
still necessary?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help