Steven Grimm wrote:
Junio C Hamano wrote:
Andreas Ericsson <ae@xxxxxx> writes:
Make "git rebase --skip" skip patches regardless of tree and index
state,
but still refuse to *start* with dirty tree or index. That way, there's
no risk of losing anything that can't be re-created unless the user asks
for it.
Sounds like a plan.
I'm unclear how that helps the usability issue here at all, though it
doesn't sound like an unreasonable change on its own merit.
Because 'git commit --skip' will not require the user to first edit the
tree so the index matches the upstream thing, and he doesn't have to
manually run 'git reset --hard' before --skip'ing.
It's a small improvement, but one that goes in the right direction.
Btw, the above sentence should've read "but still refuse to *start*
(as in, start a brand new rebase) with dirty tree or index"
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
