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

Re: Why rewrite the Subversion working copy?

From: Blair Zajac <blair_at_orcaware.com>
Date: Wed, 23 Apr 2008 09:18:25 -0700

Ben Collins-Sussman wrote:
> On Tue, Apr 22, 2008 at 6:57 PM, Justin Erenkrantz
> <justin_at_erenkrantz.com> wrote:
>> On Tue, Apr 22, 2008 at 4:28 PM, David Glasser <glasser_at_davidglasser.net> wrote:
>> > My opinion? The Subversion project shouldn't spend any more time
>> > trying to make Subversion a better version control tool for non-huge
>> > open source projects. Subversion is already decent for that task, and
>> > other tools have greater potential than it. We need to focus on
>> > making Subversion the best tool for organizations whose users need to
>> > interact with repositories in complex ways, like:
>> That's actually a pretty cool mission statement for us to focus on.
>> It's not quite the direction we set out for initially, but going
>> forward, this sort of resonates as to where we've found ourselves in
>> the spectrum of SCM tools. -- justin
> We have been groping around for a new mission statement for a year or
> two, and this is a pretty compelling one (unless we decide we want to
> become fully decentralized.).

Even if we don't go fully decentralized, having the ability to go completely
offline with a sync of a portion of the repository you need for the checkout you
have would be nice. So you could do log, blame other operations on a plane.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-23 18:19:14 CEST

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.