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

Re: Checkout every file as read-only; make some of them editable with a explicit command.

From: Kevin Williams <kevin_at_bantamtech.com>
Date: 2004-11-17 15:30:17 CET

Peter Yamamoto wrote:
> Perhaps you shouldn't rush to characterizing people as impolite...

I'm sorry you feel that way. I think in general that it's not polite to
criticize something until you've tried it, no matter whether it's
versioning methodologies or broccoli.
> The practical reason for the locks is that for files that cannot be
> merged it can help avoid wasted work...
> A person who is about to work on a file that cannot be merged (eg binary
> file of some sort such as may art file formats), can exclusively lock it
> before working on it. When this is part of the workflow, it means that
> people won't waste time working on a file only one of them will be able
> to commit.

  I've used SourceSafe, CVS, ClearCase and Subversion. I can see
benefits for each product's methodology. Binary files are certainly an
excellent reason for exclusive locks. That's why I look forward to
Subversion offering both methods.

I was just trying to avoid yet another big thread about the desire for
locking. It was not part of the original vision. Imagine how difficult
it could be to make changes to software you've written at a fundamental
level because someone else want's it that way. You've done your best to
write code the way you think is near perfect, and someone wants a
feature that goes against your point of view. It's not easy. Patience,
everyone, please.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 17 15:32:40 2004

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

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