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

Re: I miss tags

From: H. S. Teoh <hsteoh_at_quickfur.ath.cx>
Date: 2004-09-24 22:43:56 CEST

On Fri, Sep 24, 2004 at 03:34:31PM -0500, Sean Laurent wrote:
[...]
> A typical scenario we encountered follows:
>
> 1) Install team generates Build #42 of product XYZ based on revision 1000 and
> produces a label, associating XYZ_BUILD_42 with revision 1000.
> 2) Developers continue to make changes to the branch.
> 3) QA team reports a nasty, difficult bug in Build #42 that gets assigned to
> me.
> 4) At this point, the repository is up to revision 1100. To simply my ability
> to reproduce and track down the bug, I checkout XYZ_BUILD_42.
>
> Yes, this ~can~ be accomplished using branches, but it's not exactly the same
> approach. I don't need the repository to store a _copy_ of the source tree
> at revision 1000.

The repository is storing 0 diffs to copy a tree. That takes up
essentially 0 space.

> I just need to be able to easily get there, WITHOUT having
> to track down the revision number. Otherwise, we have to have documentation
> showing the mapping between build numbers and revision numbers.

You don't need to know any revision numbers. If you have tagged build
42 as /tags/xyz_build42, you could just do:

        svn co /tags/xyz_build42

Job done. No revision numbers involved.

T

-- 
Roasting my brains over a slow fire. Please do not interrupt this process.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 24 22:46:09 2004

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.