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

Re: Locking design (was Re: svn commit: r9885 - trunk/notes)

From: Patrick Dean Rusk <PRusk_at_foliage.com>
Date: 2004-05-26 19:29:02 CEST

"Greg Hudson" <ghudson@MIT.EDU> wrote:
> > + -- useful info in an in-company team. Also a note, commit-log
> > + template if you will, which could be used to describe the
> > + reason for the lock to other users. So not only 'who' and
> > + 'where', but also 'why'.
> People may find this cumbersome; I don't think other version control
> systems generally have it.

SourceSafe and PVCS have it. In ClearCase, you check out a file against a
task. So, I'd say it's pretty common in locking version control systems.

That said, I never put anything in the comments, nor have I ever worked on a
team where others did, AFAIK.

If it's not hard to do, it might be a worthwhile feature to counter the
ubiquitous "our old VCS allowed us to do that" objection that would
inevitably arise.

Patrick Rusk

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 26 19:41:03 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.