On Jul 3, 2006, at 19:12, Danny van Heumen wrote:
> *Some small scenarios worked out*
> So in order to prevent these missteps we should do the following:
>
> 1. Default to a repos layout that already has room for tags and
> branches.
>
> Possible formats:
> a. /trunk, /tags, /branches
> Use this if you're repository is used for only one project, or if
> you want a global trunk/tags/branches layout which will be
> used by
> all projects occupying to repository.
>
> b. /trunk/{project}, /tags/{project}, /branches/{project}
> The same as A, with the difference that it can be used for
> several
> projects.
>
> c. /{project}/trunk, /{project}/tags, /{project}/branches
> Use this if you want to store several projects in a single
> repository and you want to have a separate trunk/tags/branches
> layout for each of your projects.
>
> d. ... Some other layout I haven't encountered before ...
I use /trunk/{group}/{project}, /tags/{group}/{project}, /branches/
{group}/{project}
on pysvn and at work.
>
> 6. Etc.
>
Example log out:
641 | barryscott | 2006-04-23 10:21:34 | Tag 1.4.2
634 | barryscott | 2006-04-16 16:45:39 | | Fix bug in
set_default_us
627 | barryscott | 2006-04-09 16:52:51 | | Add new Client
() set and
622 | barryscott | 2006-03-26 10:53:18 | Tag 1.4.1
607 | barryscott | 2006-03-11 11:50:56 | | Add /usr/local/
lib64 to
When I look at the svn log on the trunk I want to know which tags
correspond to
which revisions. Its then easy to see if a change made it into a
particular release.
In the example I can see that the bug fixed in 634 is in 1.4.2 but
not 1.4.1
I have an implementation in pysvn WorkBench that does this, but it
relies
on the user configuring the tags paths and that tags are created
before more
commits to the trunk. From the GUI its easy to then diff any version
against
a tag.
[I realized when reading this thread that I should have used
svn_client_log to get the history of the tags dir and use the path
info to figure out
the copy_from_rev, I was using svn_client_ls to get the list of tags
and use the
date, but that is error prone.]
Barry
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 5 23:37:20 2006