On Mon, Sep 23, 2002 at 11:51:08AM -0500, Karl Fogel wrote:
> 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'. 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? :-)
Ok, I will describe the a bit more detailed:
My idea is somewhat different from what you describe.
Currently svn co needs at least one URL.
My idea would introduce a new operating mode for co which would be
used, if no URL bot only a relative directory is given. Valid options
are the same as for "normal" co mode. This means
# svn co subdir
would do the following:
- If called outside a working copy, print an error message.
- If called inside a working copy of the URL http://server/path/to/dir
- Print an error message, if subdir already exists as file or dir in
the current directory.
- Add http://server/path/to/dir/subdir to the current working copy,
if the repository contains such a subdir and there is no
conflicting file or dir in the current working copy.
- Print an error message, if http://server/path/to/dir/subdir does
not exist in the repository.
Is this list complete or do you see cases I am missing here?
The operation that should be done in the non error case should be
# svn co http://server/path/to/dir/subdir
Add '<entry name="subdir" kind="dir"/>' to .svn/entries in current dir.
What do you think of this synopsis? I am open to better ideas.
Robert Schiele Tel.: +49-621-181-2517
Received on Mon Sep 23 19:40:55 2002
- application/pgp-signature attachment: stored