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

Locking consensus(es) so far

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2004-10-13 20:58:53 CEST

Let me reiterate some agreements we seem to have reached, so far:

      - 'svn lock' only succeeds if file is up-to-date.
         (Possibly create 'svn lock --update' switch for convenience.)

      - If update would produce conflict on a 'hijacked' file:
          print warning, then choose WC fulltext, backup repos fulltext.

      - 'svn info' shows lock-token info, and also works on URLs.

And I'd like to suggest a compromise regarding whether or not
lock-messages are required:

            - client never requires lock-messages, but accepts them if
            - server doesn't require them by default, but accepts them
if presented.
            - admin can make pre-lock hook require them.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 13 21:00:17 2004

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.