Re: Recovering from commit --amend in rebase --interactive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Boaz Harrosh:

The prints are clear enough.

The problem is that you stop reading them after a while. I've been using rebase actively for a couple of years, so I don't necessary pay much attention to what it says anymore.

And besides, if I forget to do the edits in another xterm, the help text is usually gone by the time I need to continue anyway...

What?!? no, why. Just empty out the message at editor and save. It will abort any commit and do nothing.

Oh. That's useful to know next time it happens :-)


Jan Krüger:

It might be easy to miss, but it's there, right in the editor:

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and *an empty message aborts the commit*.
(Emphasis added)

Indeed. There goes thinking you know what you do after having used the tools for a long time... :-)

--
\\// Peter - http://www.softwolves.pp.se/
--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]