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

Featurerequest: autolocking binary files

From: Florian Storck <storck_at_givemepower.de>
Date: 2004-11-24 15:45:02 CET


because I just browsed the dev archive and read something about the upcoming
locking feature, I just had an idea. If its already in your mind, just
forget this mail. I not subscribed to the list, because I'm already on the
user list and didn't wanted to have another tons of mails. But my suggestion
may be of interest for you:

If the locking feature is implemented to prevent the user from accidentially
change binary files and not having merging calamities, I think it would be
useful, if these files are automatically write protected (locally) at
checkout (just to remind the user, that others might edit them and he locks
them before) or that an svn update automatically locks modified binaries on
the server. This would be of course optional via some switches. Maybe its
also better integrated in some clientapp than in the commandline tools. This
also could be finetuned via some properties.

These are just some raw ideas, there are surely several pro's and con's, but
I think such a feature could be useful in some cases, especially if the
projects are bigger and have more conflicting potential.

        Florian Storck

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 24 18:28:22 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.