From: "David Tweed" <david.tweed@gmail.com>
To: "Rogan Dawes" <lists@dawes.za.net>
Cc: "Quim K Holland" <qkholland@gmail.com>,
"gi mailing list" <git@vger.kernel.org>
Subject: Re: Time to flush Mr. Hammano?
Date: Mon, 21 Jan 2008 14:12:09 +0000 [thread overview]
Message-ID: <e1dab3980801210612k3c0a52d1l8d868a2b49f4b558@mail.gmail.com> (raw)
In-Reply-To: <47949BBD.6060308@dawes.za.net>
One other point no-one has mentioned: even if Junio were to be doing
more stabilisation than normal in a project (and I don't think he is),
version control software is one of those things like a filesystem
where paying attention to stability is really important. Unlike a
buggy music player (say), a buggy git could destroy everything up to
your last backup.
I appreciate all the work everyone in the community is currently doing
on stabilisation.
--
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"we had no idea that when we added templates we were adding a Turing-
complete compile-time language." -- C++ standardisation committee
next prev parent reply other threads:[~2008-01-21 14:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 10:10 Time to flush developer accumulated patches? Marco Costalba
2008-01-20 10:18 ` Wincent Colaiuta
2008-01-20 10:24 ` Marco Costalba
2008-01-20 10:47 ` Steffen Prohaska
2008-01-20 13:49 ` Johannes Schindelin
2008-01-20 20:05 ` Junio C Hamano
2008-01-21 11:15 ` Time to flush Mr. Hammano? Quim K Holland
2008-01-21 11:36 ` David Kastrup
2008-01-21 11:42 ` Junio C Hamano
2008-01-21 11:47 ` Imran M Yousuf
2008-01-21 11:38 ` Paolo Ciarrocchi
2008-01-21 11:39 ` Juanma Barranquero
2008-01-21 12:26 ` Johannes Schindelin
2008-01-21 13:18 ` Rogan Dawes
2008-01-21 14:12 ` David Tweed [this message]
2008-01-21 18:07 ` Marco Costalba
2008-01-21 19:13 ` Jakub Narebski
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=e1dab3980801210612k3c0a52d1l8d868a2b49f4b558@mail.gmail.com \
--to=david.tweed@gmail.com \
--cc=git@vger.kernel.org \
--cc=lists@dawes.za.net \
--cc=qkholland@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).