This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Tag reorg
DJ Delorie <dj@redhat.com> wrote:
> For each project foo, create a branches/foo directory.
>
> Within that directory, create all your ongoing tags, sub-branches,
> mergepoints, etc; with the main working copy called "trunk" or
> "branch" or something (resuling in branches/foo/trunk for example).
>
> Then, when we close the branch, we're just removing one entry from the
> branches/ directory and it all goes away together.
I think it's rather idiomatic in SVN to store the branch code itself in
/branches/foo, and the tags in /tags. We could have a /tags/foo/ tree to
hold all the tags related to foo, though. Anyway, I insist that there is no
need to have so many tags to justify such a hierarchy in the first place.
> For snapshots, for example, we'd have tags/snapshot/<branch>/YYYYMMDD
> like tags/snapshot/trunk/20051021 or tags/snapshot/gcc-4_1/20051114
Why do we need snapshot tags? Can't we generate snapshots using the -r
{2005-11-14} syntax?
--
Giovanni Bajo