[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "svn lock" crashes if editor exits without saving a lock message

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-04-09 00:05:16 CEST

"Peter N. Lundblad" <peter@famlundblad.se> writes:

> On Fri, 8 Apr 2005, Philip Martin wrote:
>>
>> The lock commit message handling is poor. First I get a blank editor
>> window with no indication of which files are to be locked, there is
>
> The files being locked are the ones specified on the command line. A
> commit is different, since it will choose what files to commit for you.

"svn rm/mkdir URL" show the command line arguments, why should lock be
different?

>> not even any indication that I should write a log message.
>>
> Same applies for propedit.

Huh? Propedit doesn't use a log message.

> I'm not sure what you want here.

A list of the paths to be locked and some text that says "write a
lock log message, all the text below the marker is ignored".

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 9 00:09:18 2005

This is an archived mail posted to the Subversion Dev mailing list.