[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Empty change log
From: |
Johan Bolmsjö |
Subject: |
[Monotone-devel] Empty change log |
Date: |
Thu, 27 Apr 2006 09:43:52 +0200 |
User-agent: |
KMail/1.9.1 |
Hello,
This is more of an question than a bug report:-)
Currently it's not possible to do:
$ mtn commit -m ""
mtn: beginning commit on branch 'test'
mtn: misuse: log message rejected: empty messages aren't allowed
But it's possible to do:
$ mtn commit -m " "
mtn: beginning commit on branch 'test'
mtn: committed revision 7ee27ff3e659d674a8008c4b7db814fcbac3968c
Now I guess that in the case you enter the commit message in the text editor
this is a protection mechanism (which I find very usefull). But when doing it
form the command line I can only assume that you folks don't like empty
commit messages. If that is the case I think that the second example should
fail too (only white space in commit message).
P.S.
This was for testing my previously reported bug, I don't do this IRL:-)
BR,
Johan
- [Monotone-devel] Empty change log,
Johan Bolmsjö <=