Robert Sfeir <email@example.com> wrote on 01/10/2005 03:53:11 PM:
> Been reading the svn manual, but can't seem to find the answer, and
> perhaps it doesn't exist.
> In CVS we used to be able to tag our repository on a certain day when
> we do a release, this effectively acted more like a marker to let us
> know we did something there, and we keep going. In Subversion tagging
> is like branching, except you don't write code to a tag beause then it
> becomes a branch, but it seems that it copies our whole repository
> into the tag part of the subversion repository. This is REALLY heavy
> considering our repository is some 20 gigs, and we do this process 3-4
> times a month.
> Is there no other way to put a 'marker' of some type in the head which
> lets us know for example that: "At tag (or marker) 011004 we deployed
> revision 6004", so that at a future point we can check out that
> particular revision, and know that we had the code as it stood then,
> but without having to copy the whole directory.
How are you defining "heavy"? The svn tag consumes very little space in
the repository and runs in a very short, constant time, that has nothing
to do with the number of files being tagged. CVS, on the other hand, can
take quite a long period of time to perform the tag operation and the tag
information is carried in every file within your repository.
So why is an svn tag "heavy"? My guess is that because the UI is showing
you the files under the tag folder you are thinking the tag did more than
it actually did.
Also, keep in mind that if you have some way of knowing your revision
number, for example, I embed it in my builds, then you really do not even
need a tag as you can just use the revision number to checkout the code as
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jan 10 22:06:47 2005