Thread (5 messages) flat view 5 messages, 3 authors, 2016-06-15

Re: git merge --abort

From: John Tapsell <hidden>
Date: 2016-06-15 22:46:16

2009/2/21 Jakub Narebski [off-list ref]:
On Sat, 21 Feb 2009, Junio C Hamano wrote:
quoted
Jakub Narebski [off-list ref] writes:
quoted
Perhaps this is the case fo "feature that waits for a user", namely
'git stash --no-reset', which would save a state just in case, perhaps
in a separate area and not refs/stash (ORIG_STASH perhaps?).
Isn't that Nana's "git stash --keep" patch posted a few weeks ago sitting
in "pu"?
Almost exactly.

When using it as a safety measure (perhaps enabled via configuration
variable, similarly to core.safecrlf or diff.autoRefreshIndex) we would
probably want to not save it in 'refs/stash' stack, but in single-use
ORIG_STATE (similar to HEAD reflog vs. ORIG_HEAD). And of course have
"git merge --abort" (or even "git pull --abort") as a porcelain.
It sounds like we have some sort of plan then.  Will Nana's patch be
committed into mainline git?  Then we can add the --abort porcelain
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help