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

SVN Tag / Branch question

From: Ahmed, Omair (GE Oil & Gas) <omair.ahmed_at_ge.com>
Date: Mon, 29 Oct 2012 18:04:22 -0400

Hello,

 

We did our first release in SVN today. I used the copy command (shown
below) to copy from /trunk to /tag. Since not everything in /trunk was
needed for this release, I had to specify the directories which were
needed.

 

Q1. Is this the normal/correct way of doing things? For the new release,
just the Docs, MKVIE and Screens dirs. were needed. The others were not.

 

Our repo structure is as follows:

 

C>svn list https://X.X.com/svn/muxbopcs_svn/trunk/MUX

 

Control/

Docs/

MKVIE/

Screens/

sem_modbus/

 

Q2. Are we better off using release branches instead of copying to
/tags?

 

Q3. Sometime down the line, if I had to re-create a view of "Release
1.6", do I just base my workspace on what's in /tags/release-1.6? Or is
there another/better way of re-creating a prior release?

 

Q4. I was also expecting /tags to contain just the new files for Release
1.6. However, that wouldn't be case, right? I have a feeling I am
confusing myself over nothing.

 

C:\>svn copy -m "Release 1.6"
https://X.X.com/svn/muxbopcs_svn/trunk/MUX/MKVIEW/

 

https://X.X.com/svn/muxbopcs_svn/tags/release-1.6/

 

 

 
Received on 2012-10-29 23:05:15 CET

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.