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

Re: feature request: checkout repositories partially

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-09-23 18:51:08 CEST

Robert Schiele <rschiele@uni-mannheim.de> writes:
> In my opinion, this is not an urgent issue, but finally I think this
> is a need. One reason, companies don't use cvs is (among other
> reasons) that it does not scale with such huge source bases and 600
> full time developers. I don't have experience, how subversion scales,
> but in my opinion, they would not even consider using it, if you
> didn't even try to support such use cases with simple stuff you can
> do.
> For the moment, I am just hand editing the .svn/entries file to do
> that. When I find the time, I will implement this myself and send you
> the results, if you agreed with me that this is a nice feature that
> you will not veto against.

The feature, as you described in your earlier mail, sounds useful, but
you might want to post a more detailed description of it before
investing coding time. That would give the group enough information
to decide in advance "Yes, a reasonable implementation of this would
become part of Subversion."

As I understand it, the behavior you're proposing is

  $ cd some-dir
  $ svn co url1 1
  $ svn co url2 2

Then 10 days later

  $ svn up

from some-dir would update 1 and 2, because they would have been
registered as workspaces in `some-dir'. We'd need to know how this
feature behaves in when some-dir is just some directory, versus when
it is a working copy. There are probably other dangling questions you
can think of, too.

IOW, what's the spec for this? :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 23 19:15:50 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.