Re: [PATCH 2/2] Re: rebase -i: explain how to discard all commits
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 21, 2011, 16:51 UTC
- Message-ID
- <7vsjwmp5cs.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.1101210801210.15247@pacific.mpi-cbg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 8 quoted lines
>> Wouldn't that suggest us that if we were to do anything to this message >> it would be a good idea to teach the user to "reset --hard" the branch >> if no commits truly needs to be replayed on top of the onto-commit? > > The important difference between rebase -i && noop on the one, and reset > --hard on the other hand is that the latter is completely unsafe. I mean, > utterly completely super-unsafe. And I say that because _this here > developer_ who is not exactly a Git noob lost stuff that way.
I think "rebase" already checks that the index and the working tree is clean before starting, so referring to "reset --hard" when "rebase -i" notices there is absolutely nothing to do is _not_ unsafe, no?