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

Re: [Issue 533] New - implement reserved checkouts

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2002-08-05 16:24:00 CEST

On Mon, 2002-08-05 at 08:37, Dave Cridland wrote:
> On Mon, 2002-08-05 at 09:27, Greg Stein wrote:
> > Oh, geez. This whole thread is way too narrowly scoped. *Everybody* is
> > talking about developers and source code. Fine, geez. No locks.

That was uncharitable. Many arguments were made with source code in
mind, but the concept of unmergeable binary formats such as CAD files
definitely came up multiple times.

> I foresee a time in the not too distant future when I'll be installing
> Subversion as an "office shared filesystem", in a purely
> non-development, non-project managed, environment.
>
> Moreover, I foresee that this is a significantly larger market.

I doubt it. Word documents may be a much more common focus of group
projects than source code, but developers are much more likely to adopt
revision control tools than non-developers. That's how we've gotten
where we are with CVS, and I don't see the situation reversing itself
any time soon.

All that said, I think I agree with Greg Stein's strategy:

  * Locks are important for some situations, but not for a CVS
    replacement. (I realize CVS has locks, but they're not commonly
    used.)

  * Hence, they won't be in 1.0 (alpha was supposed to be
    feature-complete, anyway).

  * For 90% of cases, you can get away with a system built outside of
    Subversion, which could probably be coded up in a few hours by
    someone motivated.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 16:24:56 2002

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.