Creating branch from sparse working copy, using 1.5 beta 1

[Jim Hennessy <jp...@attglobal.net>]

I would like to create a branch that represents just the directories in 
my sparse working copy, but it doesn't seem to work as I hoped.  That 
is, say my repository has these directories:

   trunk
   trunk/a
   trunk/b
   trunk/c
   branches

Now I make a working copy that is a sparse version of the trunk:

   svn checkout --depth=empty url/trunk .

Now I add a subset of the possible directories:

   svn update a b

I would like to be able to create a branch from this working copy, as in:

   svn copy . url/branches/b1

But the resulting branch has the "c" directory in it as well, even 
though it isn't in my working copy.  Is this intended, or a bug?  It 
would suit my purpose better if there was at least an option to respect 
the sparseness of my working copy.

I notice that I can do it using just URLs, such as:

   svn copy --parents url/trunk/a url/trunk/b url/branches/b1

It would sometimes be nice to be able to do it from a working copy, 
though, in order to use a mix of revisions.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Creating branch from sparse working copy, using 1.5 beta 1

[Karl Fogel <kf...@red-bean.com>]

Jim Hennessy <jp...@attglobal.net> writes:
> Karl Fogel wrote:
>> What does seem clear is that whatever our default is, there should be an
>> option to behave the other way too.  Could you file a 1.6 enhancement
>> issue for that, pointing to this mail thread?
>
> Thanks for your reply.  As you suggested, I've filed issue 3154,
> adding more on my particular needs for background info.

Thank you.  I've put it in the "1.6-consider" milestone; of course, like
anything else, it will happen faster if we get a patch for it :-).

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Creating branch from sparse working copy, using 1.5 beta 1

[Jim Hennessy <jp...@attglobal.net>]

Karl Fogel wrote:
> What does seem clear is that whatever our default is, there should be an
> option to behave the other way too.  Could you file a 1.6 enhancement
> issue for that, pointing to this mail thread?
Thanks for your reply.  As you suggested, I've filed issue 3154, adding 
more on my particular needs for background info.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Creating branch from sparse working copy, using 1.5 beta 1

[Karl Fogel <kf...@red-bean.com>]

Jim Hennessy <jp...@attglobal.net> writes:
> I would like to create a branch that represents just the directories
> in my sparse working copy, but it doesn't seem to work as I hoped.
> That is, say my repository has these directories:
>
>   trunk
>   trunk/a
>   trunk/b
>   trunk/c
>   branches
>
> Now I make a working copy that is a sparse version of the trunk:
>
>   svn checkout --depth=empty url/trunk .
>
> Now I add a subset of the possible directories:
>
>   svn update a b
>
> I would like to be able to create a branch from this working copy, as in:
>
>   svn copy . url/branches/b1
>
> But the resulting branch has the "c" directory in it as well, even
> though it isn't in my working copy.  Is this intended, or a bug?  It
> would suit my purpose better if there was at least an option to
> respect the sparseness of my working copy.
>
> I notice that I can do it using just URLs, such as:
>
>   svn copy --parents url/trunk/a url/trunk/b url/branches/b1
>
> It would sometimes be nice to be able to do it from a working copy,
> though, in order to use a mix of revisions.

Hmmmm.  It's not clear to me whether this is a bug or not; I can see
arguments both ways.

What does seem clear is that whatever our default is, there should be an
option to behave the other way too.  Could you file a 1.6 enhancement
issue for that, pointing to this mail thread?

As for actually solving your problem: I think you've found the
workaround already, and you can get mixed revisions by passing -r or
using peg revs ("@") to the cp commands.  But you're right, it would be
a *lot* more convenient if you could just do it from the working copy.

Best,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org