This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Tag reorg
Joseph S. Myers <joseph@codesourcery.com> wrote:
> as a general principle we do not know all the ways
> people might be maintaining and using branches and what uses they
> might
> have for the past tags; so we should leave their management up to the
> branch maintainers just like everything else to do with the branch.
We need to make a big difference between two things: one is *information*,
another is *policy*. My mail (about the fact that multiple merge tags are
unneded with SVN) was deliberately about *information*: we need maintainer to
*know* how SVN works. After that, we can try and come up with some policies
which would also define the meaning of "abuse" of our repository, and thus ban
those uses.
In my experience with SVN, I dare say that keeping hundreds of merge tags for
each branch could be easily be configured as an abuse of the repository, and
could be forbidden by policy. I know not everybody will agree; morevoer, those
who are new with SVN (most of our maintainers, it seems) will have to take
their time to understand the new improved procedures before they can express an
informed opinion on the matter. This is why I'm mostly into doing *information*
right now (which is also why I took the time to write and rewrite the wiki
pages).
I believe it's premature to setup policies right now (especially those who
*restrict* uses). I'm totally fine with giving each vendor full control over
their tags. I'm just saying that there *shouldn't* be so many of those tags so
discussing too much of a complex hierarchy for /tags might end up being wasted
time.
Giovanni Bajo