This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
RE: [ANNOUNCEMENT] Cygwin setup.exe bugfix release 2.510.2.2
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin-apps at cygwin dot com>
- Date: Thu, 8 Sep 2005 19:01:04 +0100
- Subject: RE: [ANNOUNCEMENT] Cygwin setup.exe bugfix release 2.510.2.2
----Original Message----
>From: Max Bowsher
>Sent: 08 September 2005 18:53
> I agree with all of the above motivation, but since a branch with no
> commits is literally just a special kind of tag, why not create the
> branch in the first place?
> If it then turns out we need it, we use it. If not, no effort is wasted,
> we just continue on trunk, and create a new release branches at each
> release from trunk.
But we would be wasting magic revision numbers! ;)
Seriously though, since the (normal tag for branchpoint) + (branch tag
based on that normal tag) paradigm is so widespread, I vote for making it
just an ordinary tag that we can base a branch on only if we ever need to.
Having lots of unused branches doesn't cost much resource-wise, I admit, but
it is cluttered and confusing when you start going into the cvs log/history
and find loads and loads of branch tags left, right and centre. And it
causes the drop-down box on the cvsweb interface to fill up with loads of
entries!
cheers,
DaveK
--
Can't think of a witty .sigline today....