You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Robert Schiele <rs...@uni-mannheim.de> on 2002/09/22 09:39:13 UTC
feature request: checkout repositories partially
Hello,
I am using the following CVS feature that is not possible with SVN
without hand editing some files. (At least I don't know how.)
Assume you have a repository with the following structure:
project/
Makefile
Rules.make
a/
[many files and subdirs]
b/
[many files and subdirs]
c/
[many files and subdirs]
Further assume, c/ includes some stuff that has to be kept private,
e.g. rsa keys, and so shouldn't be checked out on clients that are
publicly accessible.
With CVS I do:
# CVSROOT=server:/path/to/repos export
# cvs co files/{Makefile,Rules.make,a,b}
Now I have all what I need, but prevent checkout of c/.
The drawback with cvs is that you never should run "cvs update -d"
from the project/ dir, but I can live with that.
With SVN this seems not to be possible.
I tried:
# svn co -N https://server/repos
I wanted to add subdirs later, but I didn't find a possibility to do
so.
It would be nice to be able to just do a
# svn co a
# svn co b
Without an absolute URL this should mean, add this subdir from the
server to the client workspace.
What do you think about that idea?
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Mon, Sep 23, 2002 at 09:29:48AM -0700, Kevin Pilch-Bisson wrote:
> Quoting Robert Schiele <rs...@uni-mannheim.de>:
>
> > 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.
> >
> You may not want to do that. You'll run into the same problem I described if
> someone commits something in one of the directories you remove
> from .svn/entries and you try to update.
Ok, I see the problem you mention, but I still _want_ what I said.
Sure I additionally want that bug to be fixed.
As a workaround for the meantime: It still works if I update in a
subtree that is not an ancestor of the one with the mentioned commit,
doesn't it?
> A patch to deal with the situation properly (as I described in my other mail),
> would be most appreciated :)
I believe that, but as I am not familiar with the svn sources yet, I
assume a developer that is will be much faster in fixing it.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
Quoting Robert Schiele <rs...@uni-mannheim.de>:
> 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.
>
You may not want to do that. You'll run into the same problem I described if
someone commits something in one of the directories you remove
from .svn/entries and you try to update.
A patch to deal with the situation properly (as I described in my other mail),
would be most appreciated :)
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson
kevin@pilch-bisson.net
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Mon, Sep 23, 2002 at 07:40:22PM +0200, Sander Striker wrote:
> It's a bit more specific than that the way I understand it.
> Consider the repos to be layed out like:
>
> A/
> B/
> f1
> C/
> f2
> f3
>
> Doing:
>
> $ svn co -N <baseurl>/A
>
> gives you:
>
> A/
> f3
>
> as a working copy.
>
> Now, enter A and do:
>
> $ svn co B [the new feature Robert is suggesting]
>
> This gets you:
>
> A/
> B/
> f1
> f3
>
> where B is in the entries file of A and will therefor
> be automatically updated with svn up in A.
That's exactly what I mean.
> > 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.
That's correct.
> > IOW, what's the spec for this? :-)
>
> I'll leave the rest up to Robert then ;)
I hope my other mail has all the needed information. Otherwise feel
free to ask.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Robert Schiele <rs...@uni-mannheim.de> writes:
> I will do that, if you found it usefull, as soon as the one
> responsible for that confirms my "observer" role for the project.
Done :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Mon, Sep 23, 2002 at 12:27:23PM -0500, Karl Fogel wrote:
> Robert Schiele <rs...@uni-mannheim.de> writes:
> > 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
> > it will:
> >
> > - 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?
>
> Ah, I understand it better now, thanks. So this would be most useful
> in a directory that had been checked out with -N first (so the main
> thing is to get -N working right). The subsequent checkouts are about
> undoing the effect of the -N, a little bit at a time :-).
>
> Thanks for the description. Given a working -N, imho this is a
> completely intuitive behavior for follow-up checkouts within that
> directory. Would you like to add your comments to
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=695
>
> (the checkout -N issue)?
I will do that, if you found it usefull, as soon as the one
responsible for that confirms my "observer" role for the project.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Robert Schiele <rs...@uni-mannheim.de> writes:
> 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
> it will:
>
> - 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?
Ah, I understand it better now, thanks. So this would be most useful
in a directory that had been checked out with -N first (so the main
thing is to get -N working right). The subsequent checkouts are about
undoing the effect of the -N, a little bit at a time :-).
Thanks for the description. Given a working -N, imho this is a
completely intuitive behavior for follow-up checkouts within that
directory. Would you like to add your comments to
http://subversion.tigris.org/issues/show_bug.cgi?id=695
(the checkout -N issue)?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Mon, Sep 23, 2002 at 11:51:08AM -0500, Karl Fogel wrote:
> Robert Schiele <rs...@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? :-)
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
it will:
- 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
similar as:
# 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
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
RE: feature request: checkout repositories partially
Posted by Sander Striker <st...@apache.org>.
> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> Sent: 23 September 2002 18:51
> Robert Schiele <rs...@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'.
It's a bit more specific than that the way I understand it.
Consider the repos to be layed out like:
A/
B/
f1
C/
f2
f3
Doing:
$ svn co -N <baseurl>/A
gives you:
A/
f3
as a working copy.
Now, enter A and do:
$ svn co B [the new feature Robert is suggesting]
This gets you:
A/
B/
f1
f3
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 ;)
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Robert Schiele <rs...@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? :-)
Thanks,
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Mon, Sep 23, 2002 at 10:52:40AM -0500, Ben Collins-Sussman wrote:
> Here's a silly question: can't our 'modules' feature solve your
> problem for the time being?
>
> Lay out your repository like this:
>
> /a
> /b
> /c
> /project/
> /modules/
> /fullmodule
> /partialmodule
>
> fullmodule and partialmodule can simply be copies of 'project'. Now
> set the 'svn:externals' property on the two module directories. The
> partialmodule automatically adds a and b subdirs, and the fullmodule
> adds all three subdirs.
>
> Wouldn't that work?
I would consider this a workaround. But at least for the remote
future it would in my opinion be much cleaner to be able to do
decisions that are related to the client side easily with the client
and not with an ugly workaround in the repository.
Assume you have a rather huge project where developers only want to
checkout the stuff they work on regularly. This is not unrealistic,
if you had 800MB sources. Then you don't want to make modules for the
power set of all subprojects.
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.
Robert
BTW: These numbers are not somewhat fantastic, but realistic numbers
from a project I was involved to.
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Ben Collins-Sussman <su...@collab.net>.
Robert Schiele <rs...@uni-mannheim.de> writes:
> project/
> Makefile
> Rules.make
> a/
> [many files and subdirs]
> b/
> [many files and subdirs]
> c/
> [many files and subdirs]
>
> Further assume, c/ includes some stuff that has to be kept private,
> e.g. rsa keys, and so shouldn't be checked out on clients that are
> publicly accessible.
Wow, what a long thread. Everyone seems to be talking about how 'svn
co -N' doesn't work properly.
Here's a silly question: can't our 'modules' feature solve your
problem for the time being?
Lay out your repository like this:
/a
/b
/c
/project/
/modules/
/fullmodule
/partialmodule
fullmodule and partialmodule can simply be copies of 'project'. Now
set the 'svn:externals' property on the two module directories. The
partialmodule automatically adds a and b subdirs, and the fullmodule
adds all three subdirs.
Wouldn't that work?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Sun, Sep 22, 2002 at 01:00:06PM -0400, Garrett Rooney wrote:
> if you do a nonrecursive checkout of a dir, you don't actually get any
> of the contents of the directory checked out. that can't be right...
I do. This works for me.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
Quoting Garrett Rooney <ro...@electricjellyfish.net>:
> On Sunday, September 22, 2002, at 01:33 PM, Sander Striker wrote:
>
> >> From: Garrett Rooney [mailto:rooneg@electricjellyfish.net]
> >> Sent: 22 September 2002 19:00
> >
> > [...]
> >> if you do a nonrecursive checkout of a dir, you don't actually get any
> >> of the contents of the directory checked out. that can't be right...
> >> if that's the intended behaviour, it's pretty useless, as you can't
> >> actually do anything with the resulting working copy.
> >>
> >> i thought the way it was supposed to work was that you do a 'svn co -N
> >> http://foo.com/repos', and that gets you all the contents of that top
> >> level directory, but none of the contents of any subdirectories of it.
> >> thus one could have a top level directory that has a README or
> >> somethign in it (like svn.collab.net/repos/svn does), and you'd do a
> >> nonrecursive checkout of that dir to get that README so you could edit
> >> it without having to check out the whole damn repos.
> >
> > And that is what it does. Currently a non-recursive checkout of
> > a directory gets you that directory and its contents, minus its
> > subdirectories.
> >
> > These subdirectories _aren't_ in the .svn/entries file either, so
> > the working copy has no notion that there are (deliberate) absent
> > subdirectories.
>
> ahh, ok, the repos i tested on here didn't have anything but
> directories in the dir i tried to check out.
>
> if this is the case, then perhaps issue 695 is no longer really valid?
>
It's still valid. The problem is that if something changes in a subdir, the
server sends the changes, and the client chokes, since by this point it's
never heard of the subdirs.
There are two possible solutions that I can think of.
1) The client maintains state, and sends to the server during an update: "I
have base-rev X, but I'm not interested in changes within foo, bar, or bazz."
The server sends a normal update response, but excludes the parts the client
said it wasn't interested in.
2) The client maintains state, and sends a normal update request, then filters
the results for the subdirs it's not interested in.
I think 1 is a preferred solution, but two affects less code.
Just in case you wanted one, heres a repro recipe. If someone could add this
to the issue, it might help me not have to answer this question every month or
so. (I guess if I just fixed that would do it too :)
svnadmin create repo
svn co file://`pwd`/repo wc1
cd wc1
mkdir a
touch foo
touch a/bar
svn add a
svn add foo
svn add a/bar
svn ci
cd ..
svn co -N file://`pwd`/repo wc2 # get only foo here.
cd wc1/a
vim bar # make some changes
svn ci
cd ../wc2
svn up #watch the client choke because it's never heard of a/bar.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson
kevin@pilch-bisson.net
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Sunday, September 22, 2002, at 01:33 PM, Sander Striker wrote:
>> From: Garrett Rooney [mailto:rooneg@electricjellyfish.net]
>> Sent: 22 September 2002 19:00
>
> [...]
>> if you do a nonrecursive checkout of a dir, you don't actually get any
>> of the contents of the directory checked out. that can't be right...
>> if that's the intended behaviour, it's pretty useless, as you can't
>> actually do anything with the resulting working copy.
>>
>> i thought the way it was supposed to work was that you do a 'svn co -N
>> http://foo.com/repos', and that gets you all the contents of that top
>> level directory, but none of the contents of any subdirectories of it.
>> thus one could have a top level directory that has a README or
>> somethign in it (like svn.collab.net/repos/svn does), and you'd do a
>> nonrecursive checkout of that dir to get that README so you could edit
>> it without having to check out the whole damn repos.
>
> And that is what it does. Currently a non-recursive checkout of
> a directory gets you that directory and its contents, minus its
> subdirectories.
>
> These subdirectories _aren't_ in the .svn/entries file either, so
> the working copy has no notion that there are (deliberate) absent
> subdirectories.
ahh, ok, the repos i tested on here didn't have anything but
directories in the dir i tried to check out.
if this is the case, then perhaps issue 695 is no longer really valid?
-garrett
--
garrett rooney Remember, any design flaw you're
rooneg@electricjellyfish.net sufficiently snide about becomes
http://electricjellyfish.net/ a feature. -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: feature request: checkout repositories partially
Posted by Sander Striker <st...@apache.org>.
> From: Garrett Rooney [mailto:rooneg@electricjellyfish.net]
> Sent: 22 September 2002 19:00
[...]
> if you do a nonrecursive checkout of a dir, you don't actually get any
> of the contents of the directory checked out. that can't be right...
> if that's the intended behaviour, it's pretty useless, as you can't
> actually do anything with the resulting working copy.
>
> i thought the way it was supposed to work was that you do a 'svn co -N
> http://foo.com/repos', and that gets you all the contents of that top
> level directory, but none of the contents of any subdirectories of it.
> thus one could have a top level directory that has a README or
> somethign in it (like svn.collab.net/repos/svn does), and you'd do a
> nonrecursive checkout of that dir to get that README so you could edit
> it without having to check out the whole damn repos.
And that is what it does. Currently a non-recursive checkout of
a directory gets you that directory and its contents, minus its
subdirectories.
These subdirectories _aren't_ in the .svn/entries file either, so
the working copy has no notion that there are (deliberate) absent
subdirectories.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Sunday, September 22, 2002, at 12:51 PM, Robert Schiele wrote:
> On Sun, Sep 22, 2002 at 10:20:17AM -0400, Garrett Rooney wrote:
>> On Sunday, September 22, 2002, at 09:53 AM, Nuutti Kotivuori wrote:
>>
>>> Robert Schiele wrote:
>>>> I tried:
>>>>
>>>> # svn co -N https://server/repos
>>>>
>>>> I wanted to add subdirs later, but I didn't find a possibility to do
>>>> so.
>>>
>>> That sounds like quite the right solution. And your problem most
>>> likely was that the -N option to checkout is not working too well
>>> yet. Hopefully it will be better in the future.
>>
>> i believe there's an issue filed about that already. checking out
>> with
>> --nonrecursive isn't sticky, so when you next do an svn up, you get
>> everything under it...
>
> No I don't. At least not with 0.14.3. I tried that.
you appear to be correct. although, i think it's more that other
things are broken, rather than it functioning as intended...
if you do a nonrecursive checkout of a dir, you don't actually get any
of the contents of the directory checked out. that can't be right...
if that's the intended behaviour, it's pretty useless, as you can't
actually do anything with the resulting working copy.
i thought the way it was supposed to work was that you do a 'svn co -N
http://foo.com/repos', and that gets you all the contents of that top
level directory, but none of the contents of any subdirectories of it.
thus one could have a top level directory that has a README or
somethign in it (like svn.collab.net/repos/svn does), and you'd do a
nonrecursive checkout of that dir to get that README so you could edit
it without having to check out the whole damn repos.
the issue i was thinking of, for the record, is 695.
-garrett
--
garrett rooney Remember, any design flaw you're
rooneg@electricjellyfish.net sufficiently snide about becomes
http://electricjellyfish.net/ a feature. -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Robert Schiele <rs...@uni-mannheim.de>.
On Sun, Sep 22, 2002 at 10:20:17AM -0400, Garrett Rooney wrote:
> On Sunday, September 22, 2002, at 09:53 AM, Nuutti Kotivuori wrote:
>
> >Robert Schiele wrote:
> >>I tried:
> >>
> >># svn co -N https://server/repos
> >>
> >>I wanted to add subdirs later, but I didn't find a possibility to do
> >>so.
> >
> >That sounds like quite the right solution. And your problem most
> >likely was that the -N option to checkout is not working too well
> >yet. Hopefully it will be better in the future.
>
> i believe there's an issue filed about that already. checking out with
> --nonrecursive isn't sticky, so when you next do an svn up, you get
> everything under it...
No I don't. At least not with 0.14.3. I tried that.
Robert
--
Robert Schiele Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Re: feature request: checkout repositories partially
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Sunday, September 22, 2002, at 09:53 AM, Nuutti Kotivuori wrote:
> Robert Schiele wrote:
>> I tried:
>>
>> # svn co -N https://server/repos
>>
>> I wanted to add subdirs later, but I didn't find a possibility to do
>> so.
>
> That sounds like quite the right solution. And your problem most
> likely was that the -N option to checkout is not working too well
> yet. Hopefully it will be better in the future.
i believe there's an issue filed about that already. checking out with
--nonrecursive isn't sticky, so when you next do an svn up, you get
everything under it...
-garrett
--
garrett rooney Remember, any design flaw you're
rooneg@electricjellyfish.net sufficiently snide about becomes
http://electricjellyfish.net/ a feature. -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: feature request: checkout repositories partially
Posted by Nuutti Kotivuori <na...@iki.fi>.
Robert Schiele wrote:
> I tried:
>
> # svn co -N https://server/repos
>
> I wanted to add subdirs later, but I didn't find a possibility to do
> so.
That sounds like quite the right solution. And your problem most
likely was that the -N option to checkout is not working too well
yet. Hopefully it will be better in the future.
-- Naked
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org