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

Re: Similating "label" feature in Subversion?

From: Jean-Claude Antonio <jcantonio_at_arcetis.com>
Date: 2007-08-27 20:14:49 CEST

There are 2 ways you can achieve this.

With Branches
projects
    /trunk
    /branches
        /2007-05-01; Mini-effort on feature A
        /2007-05-15; Mini-effort on feature B
    /tags

You can always determine the branchpoints (the revision of the creation
of you branch) of your branches :
by using svn log --stop-on-copy
so you can use the svn update -r branchpoint

Or if you want you can create Tags.
- Create your branch, then create you tag (make it then RO by a script
or with authorization)
- Start develop in your branch.
Remember that svn copy is cheap.

projects
    /trunk
    /branches
        /Mini-effort on feature A
        /Mini-effort on feature B
    /tags
        /2007-05-01; Mini-effort on feature A - init
        /2007-05-04; Mini-effort on feature A - completed
        /2007-05-15; Mini-effort on feature B - init
        /2007-05-04; Mini-effort on feature B - completed

then use svn co path_to_tag_name to go back to.
 
Jean-Claude

Bicking, David (HHoldings, IT) a écrit :
>
> Thank you for your reply. What you suggest is to use the revision. However, I am talking about labeling a revision with a human-readable, searchable text fragment. Some SCM tools permit labels on individual files at specific revisions, though these systems usually keep revisions per file, not per repository.
>
> Thus, on mainline, we would be able to get a list of all labels on the XYZ folder (which is a whole application project) that might look like this:
>
> Branch: 2007-05-01; Mini-effort on feature A
> Merge: 2007-05-04; Mini-effort on feature A completed
> Branch: 2007-05-15; Mini-effort on feature B
> Merge: 2007-05-04; Mini-effort on feature B completed
> Rollback Point: 2007-04-04; This is a safe rollback point during development of feature X.
>
> The above is an example in which I can identify a sort of timeline of development. In the last example, I might have placed that there on the project because we're going to try something particularly experimental over a period of days and want to easily see which revision represents the last good place. Of course, branches could be used for that purpose, too. In some other SCM tools, a rollback to a revision or label results in the elimination of all revisions of the flagged files after that point. I realize that is not the case with Subversion.
>
> --
> David
>
>
>
> *************************************************************************
> This communication, including attachments, is
> for the exclusive use of addressee and may contain proprietary,
> confidential and/or privileged information. If you are not the intended
> recipient, any use, copying, disclosure, dissemination or distribution is
> strictly prohibited. If you are not the intended recipient, please notify
> the sender immediately by return e-mail, delete this communication and
> destroy all copies.
> *************************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 27 20:16:24 2007

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