RE: SVN Tag / Branch question
From: Ahmed, Omair (GE Oil & Gas) <omair.ahmed_at_ge.com>
Date: Tue, 30 Oct 2012 14:10:07 -0400
Bob,
You are correct in making the statement below.
However, what's confusing is that when I copied the Docs directory from /trunk to /tags/release-1.6, the directory included files from the previous release also. Basically, I was expecting to see just the new files. I am trying to understand how that happened and how to prevent.
"Also, if you released your product from a certain svn revision, aren't ALL the files in that revision part of that release version?"
-----Original Message-----
> Hello,
Not sure what you mean by "not needed". However, you don't save anything by not just copying trunk to tag. Since svn uses "cheap copies" copying the full trunk folder doesn't take any more space than copying certain folders. Also, if you released your product from a certain svn revision, aren't ALL the files in that revision part of that release version?
> Our repo structure is as follows:
To svn a copy is a copy. tags and branches are semantic names. In general a tag isn't ever committed to. But, this is only by convention.
> Q3. Sometime down the line, if I had to re-create a view of "Release
I would copy the tag to a branch and work from the branch.
> Q4. I was also expecting /tags to contain just the new files for
Basically, all a copy is, is a pointer to the location that it copied. So, the state of the path you copy to includes everything from the source path. But, once again, it is a cheap copy so no files are really copied.
BOb
|
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.