[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Branching Noob Question

From: Erik Hemdal <erik_at_comprehensivepower.com>
Date: 2006-08-16 22:25:38 CEST

> From: Rob Wilkerson [mailto:r.d.wilkerson@gmail.com]
>
> This is particularly remedial, I know (I almost hate to ask
> the question), but I can't quite understand what I'm doing
> wrong. I'm trying to create a branch from the trunk and,
> after the branch is complete, the branch includes the trunk
> directory. Using this command
>
> svn cp -m "Creating a 3.5.5 maintenance branch"
> http://example.com/repos/myrepos/trunk/
> http://example.com/repos/myrepos/branches/maint/3.5.5/
>
> I end up with the following:
>
> example.com/branches/maint/currentversion/trunk
>
> What I want, of course, is for the /trunk level to go away
> and its contents to live directly beneath the /currentversion
> directory. I'm new to Subversion (obviously), but I've done
> this before with the expected results. I guess I just got
> lucky, though, because I have no idea what I did differently.
>
> Thanks for your help.

Here's another one asking the same question. I can usually get this right
if I use TortoiseSVN and really act dumb about it (TortoiseSVN > Branch/tag
usually does the Right Thing unless I have already created the branch).

But when I go about trying to deliberately make a branch, I usually mess it
up in the way Rob describes. I've not been able to really understand the
way SVN wants me to do this. And I would appreciate a pointer to somewhere
where a good explanation can be found.

Rob, does a question stop being dumb when two people ask it? Let's hope so,
shall we?

Erik

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 16 22:41:46 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.