From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Christoph Lameter <clameter@sgi.com>
Cc: Thomas Glanzmann <thomas@glanzmann.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: GIT Packages for Debian Etch
Date: Tue, 19 Jun 2007 18:37:51 -0500 [thread overview]
Message-ID: <467868CF.30606@mnsu.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0706191215570.7008@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Tue, 19 Jun 2007, Thomas Glanzmann wrote:
>
> The other choice that we developers usually make is to run either testing
> or unstable. "stable" is a synonym for obsolete ;-).
>
>
I'm just not going to let this go. Stable is synonymous with, well
ummm, "stable." That means that I don't have 3000 changes a month, it's
secure and the unexpected doesn't happen. It means I can write a
lecture explaining how git works. ...do updates... then expect my
lecture to still work the next day. It means writing local shell
scripts and expecting them to work until the NEXT stable release without
changes. It means knowing what things WILL break if and when I do go to
the next version.
Stable is a CHOICE not a punishment.
--
Jeffrey Hundstad
PS. Running unstable on my laptop... and running stable on my servers.
next prev parent reply other threads:[~2007-06-19 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 21:25 GIT Packages for Debian Etch Thomas Glanzmann
2007-06-18 21:27 ` Pierre Habouzit
2007-06-18 21:34 ` Thomas Glanzmann
2007-06-18 21:48 ` Carlo Wood
2007-06-18 21:56 ` Thomas Glanzmann
2007-06-18 22:03 ` Thomas Glanzmann
2007-06-18 22:04 ` Carlo Wood
2007-06-18 22:08 ` Thomas Glanzmann
2007-06-18 23:18 ` Christoph Lameter
2007-06-18 23:36 ` Roland Dreier
2007-06-19 6:13 ` Thomas Glanzmann
2007-06-19 19:16 ` Christoph Lameter
2007-06-19 23:37 ` Jeffrey Hundstad [this message]
2007-06-20 1:33 ` Kyle Moffett
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=467868CF.30606@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@glanzmann.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.