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

Re: locking schedule-add files (was Re: svn commit: r13308)

From: Daniel Patterson <danpat_at_danpat.net>
Date: 2005-03-09 20:57:50 CET

Ben Collins-Sussman wrote:
> I think the best thing to do is just make 'svn lock' deliberately error
> out on a schedule add file. The message would be something like, "Only
> files in already in the repository can be locked."

   Does this include renaming files?

   I.e. which of the following (if either) will generate an error:

    $ svn co file:///repos/trunk
    U trunk/readme.txt
    $ cd trunk
    $ svn lock readme.txt
    svn: readme.txt locked with token XYZ
    $ svn mv readme.txt readme2.txt
    ???? what happens here is it ok to rename a locked file?


    $ svn co file:///repos/trunk
    U trunk/readme.txt
    $ cd trunk
    $ svn mv readme.txt readme2.txt
    A readme2.txt
    D readme.txt
    $ svn lock readme2.txt
    ???? according to your satement above, this'll throw an error,
         but should it?

   So two questions:
     1) Is it ok to rename a file that's locked?
     2) Is it ok to lock a file that's renamed?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 9 21:01:27 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.