Fwd: [Bug] - Processing commit message after amend

Hi,

I have stumbled on a weird bug. At work, we use redmine as an issue tracker and its task are marked by a number starting with #. When I commit some work and write #1234 in the message, it works. However, later on when I remember that I forgot to add some files and amend the commit, vim appears and I cannot perform the commit because the message starts with # which is a comment in vim and thus I get an error that my commit message is empty.

Steps to reproduce:
1) commit a file
git commit File1.txt -m "#1234 documentation added"

2) amend previous commit
git commit File2.txt -- amend

3) go for :wq right away

4) an error that the message is empty appears
"Aborting commit due to empty commit message"

However, if you use amend and no edit option, it works git commit --amend --no-edit

We use git for Windows downloaded here: http://git-scm.com/downloads

The problem appears in Windows command line. I have not tested it anywhere else. The OS is Windows Server 2008 R2 Datacenter.

Cheers from cloudy Prague Michal Staša

Santhos.net www.santhos.net

+420 773 454 793 michal.stasa@santhos.net