From: Matt Mackall <mpm@selenic.com>
To: Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Enough with the ad-hoc naming schemes, please
Date: Mon, 18 Oct 2004 13:08:51 -0500 [thread overview]
Message-ID: <20041018180851.GA28904@waste.org> (raw)
Dear Linus,
I can't help but notice you've broken all the tools that rely on a
stable naming scheme TWICE in the span of LESS THAN ONE POINT RELEASE.
In both cases, this could have been avoided by using Marcello's 2.4
naming scheme. It's very simple: when you think something is "final",
you call it a "release candidate" and tag it "-rcX". If it works out,
you rename it _unmodified_ and everyone can trust that it hasn't
broken again in the interval. If it's not "final" and you're accepting
more than bugfixes, you call it a "pre-release" and tag it "-pre".
Then developers and testers and automated tools all know what to
expect.
--
Mathematics is the supreme nostalgia of our time.
next reply other threads:[~2004-10-18 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 18:08 Matt Mackall [this message]
2004-10-18 18:38 ` Enough with the ad-hoc naming schemes, please cliff white
2004-10-18 20:44 ` Russell King
2004-10-19 9:06 ` Geert Uytterhoeven
2004-10-18 20:52 ` Christoph Hellwig
2004-10-19 16:18 ` Martin J. Bligh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041018180851.GA28904@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox