RE: Help needed with a unique type of branch creation

Hi all,

I just thought I'd mention that I have now also tried the following variant which still branched the HEAD instead of revision 10000:

$ svn copy -r 10000 svn://domain.com/trunk svn://domain.com/branches/temp

Regards,

-- 
Mun
> Hi Stefan,
> 
> Thank you very much for your reply.
> Please see my comments below.
> 
> > On Wed, Mar 04, 2020 at 04:45:45AM +0000, Mun Johl wrote:
> > > Hi all,
> > >
> > > Off of trunk in our repo are various directories.  I am trying to
> > > branch a
> > specific revision of two of the directories and am not being
> > successful ... the branch is always off of the HEAD revision.  Here's one
> attempt:
> > >
> > > $ svn mkdir ^/branches/temp
> > > $ svn copy -r 10000 svn://domain.com/trunk/dir-x
> > > svn://domain.com/branches/temp $ svn copy -r 10000
> > > svn://domain.com/trunk/dir-y svn://domain.com/branches/temp
> >
> > > I'd rather not branch the entire trunk due to it's size and mostly
> > > unneeded
> > files.
> >
> > What you are trying to do may look like a benefit in the short term.
> > But once you run sync merges from trunk, or merge your changes back to
> > trunk, it will work a lot better if SVN sees your branch as a full copy of trunk.
> >
> > So I would recommend to always branch the entire trunk.
> 
> [Mun]  I decided to heed your advice and do something like this:
> $ svn copy svn://domain.com/trunk_at_10000
> svn://domain.com/branches/temp
> 
> However, that still branched the HEAD revision instead of revision 10000.  Not
> that it should matter--I don't think--but I executed the command from a
> working directory that was at revision 10000.
> 
> > On the server this does not use any additional space.
> 
> [Mun]  Thanks for the reminder :)
> 
> > On the client you can make your working copy "shallow" (also called
> > "sparse") to avoid the space issues and unneeded files.
> > See
> > http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html
> 
> [Mun] I have made that so.  Now I only need to figure out how to branch the
> specific revision I need rather than HEAD.  Note that we are using "svn,
> version 1.8.19 (r1800620)".
> 
> Best regards,
> 
> --
> Mun