On Tue, 27 May 2003 16:19:20 -0500, Nicholas Riley <njriley@uiuc.edu> wrote:
> On Tue, May 27, 2003 at 04:17:07PM -0500, Nicholas Riley wrote:
>> How about additionally checking for an empty log message? Then you'd
>> get:
>>
>> Commit changes using an empty log message? (yes/no/edit)
>>
>> If someone really wanted an empty log message on a regular basis, they
>> could just use svn commit -m ''. And since the confirmation doesn't
>> always appear, it would actually be meaningful.
>
> Whoops, I should have tested the existing behavior first. All that
> needs to change is the definition of 'empty'. The current prompt is:
>
> Log message unchanged or not specified
> a)bort, c)ontinue, e)dit
>
> If log messages consisting entirely of whitespace counted as 'not
> specified', then this would work well for editors which add trailing
> newlines, etc.
I think this is a good idea. It would also deal with my issue. If
someone wanted the option to abort their commit, they could just make
sure to have a log message which was (at most) whitespace. It would
also be consistent with the current behaviour, as Nicholas says.
Of course, this might not be trivial to implement.
Faheem.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 27 23:43:25 2003