hello,
bug is easily reproducible by
foo
git add foo
git commit --amend
:q!
1 files changed, 1 insertions(+), 8 deletions(-)
create mode 100644 test
git --version
git version 1.7.0.2
aboves is usage with vim as patch editor.
The expected behaviour would be to have not foo add to repo.
afair this feature^Wbug exists since loooong.
thanks + kind regards
--
maks
On Mar 22, 2010, at 12:36 AM, maximilian attems wrote:
bug is easily reproducible by
quoted
foo
git add foo
git commit --amend
:q!
1 files changed, 1 insertions(+), 8 deletions(-)
create mode 100644 test
git --version
git version 1.7.0.2
aboves is usage with vim as patch editor.
The expected behaviour would be to have not foo add to repo.
afair this feature^Wbug exists since loooong.
Vim returns 0 even if quit with :q!. Killing vim from another terminal causes this:
Vim: Caught deadly signal TERM
Vim: Finished.
error: /Users/brian/bin/vim died of signal 15
error: There was a problem with the editor '/Users/brian/bin/vim'.
Please supply the message using either -m or -F option.
If you want to abort committing while editing the message, delete the entire message (in Vim: "0dG:wq^M") and git will reply "Aborting commit due to empty commit message."
~~ Brian
On Mar 22, 2010, at 1:16 AM, Brian Gernhardt wrote:
If you want to abort committing while editing the message, delete the entire message (in Vim: "0dG:wq^M") and git will reply "Aborting commit due to empty commit message."
Oops. Obviously I meant "ggdG:wq^M".
Also, a quick search of :help and testing reveals that ":cq" causes Vim to exit with non-zero status which will cause git to abort the commit.
~~ Brian
On Mon, 22 Mar 2010, Brian Gernhardt wrote:
On Mar 22, 2010, at 1:16 AM, Brian Gernhardt wrote:
quoted
If you want to abort committing while editing the message, delete the entire message (in Vim: "0dG:wq^M") and git will reply "Aborting commit due to empty commit message."
Oops. Obviously I meant "ggdG:wq^M".
Also, a quick search of :help and testing reveals that ":cq" causes Vim to exit with non-zero status which will cause git to abort the commit.
thanks for the pointer this is indeed very helpful. :)
kept hiting that bug in stressy situations, good to know a way out.