Your message dated Sun, 21 Oct 2007 22:46:51 +0200
with message-id <[EMAIL PROTECTED]>
and subject line #178696,Fix for Bug#71502 is borken itself!
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cvs
Version: 1.11.1p1debian-8.1
Severity: normal
Joey's fix for #71502 has broken original functionality we're
using. By changing the modtime of the commit message, "cvs commit"
will _always_ end up committing your changes. That means that (for
example) forgetting to type in a commit message is no longer picked
up. It's now also impossible to change your mind after starting to
commit files, another common use.
If you're going to be worrying about typeahead, then use cvs -m <msg>
commit - that's what it's for. Or alternatively we should find a
better way to tell if the commit message has actually been modified
since creation - maybe do a bytewise compare if the before and after
mtimes are identical?
--
Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED]
Use Debian GNU/Linux - upgrade your Windoze box today! http://www.debian.org/
"Can't keep my eyes from the circling sky,
"Tongue-tied & twisted, Just an earth-bound misfit, I..."
--- End Message ---
--- Begin Message ---
Version: 1:1.12.13-8
When entering a blank commit message the following text is shown:
> Log message unchanged or not specified
> a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs
> Action: (continue)
Which gives you the ability to stop the commit or re-edit your commit
message.
--
Lior Kaplan
[EMAIL PROTECTED]
--- End Message ---
