> From: Karl Fogel [mailto:email@example.com]
> Sent: 23 September 2002 18:51
> Robert Schiele <firstname.lastname@example.org> 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'.
It's a bit more specific than that the way I understand it.
Consider the repos to be layed out like:
$ svn co -N <baseurl>/A
as a working copy.
Now, enter A and do:
$ svn co B [the new feature Robert is suggesting]
This gets you:
where B is in the entries file of A and will therefor
be automatically updated with svn up in A.
> We'd need to know how this
> feature behaves in when some-dir is just some directory, versus when
> it is a working copy.
It works only in working copies in my mind. Otherwise you end up creating
administrative areas in normal directories.
> There are probably other dangling questions you
> can think of, too.
> IOW, what's the spec for this? :-)
I'll leave the rest up to Robert then ;)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Sep 23 19:29:33 2002