From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Worrisome bug trend
Date: Tue, 27 Feb 2007 22:07:10 +0100 [thread overview]
Message-ID: <200702272207.10453.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <7vodnfg4sy.fsf@assigned-by-dhcp.cox.net>
tisdag 27 februari 2007 13:31 skrev Junio C Hamano:
> I was reviewing the bugs we fixed since v1.5.0 and noticed
> almost all of them are ancient ones. We do have small number of
> bugs introduced by recently added commands and options, but I
> see quite a few that are from 2005.
>
> I take that as a sign that git hasn't been exercised well and
> yet more ancient bugs are sleeping, waiting to be triggered, not
> as a sign that we are very careful and adding only small number
> of risky new code in the releases.
>
> Which is kind of depressing...
When bugs gets fixed and reappear, that's the time to start worry. That old
bugs gets fixed is a very good sign. It means Git is being tested by users
that care. Git is very feature rich and considering that, it's amazing that
is isn't completly bugridden with a 10K known unfixed bugs. That would be
depressing, the current state isn't.
-- robin
prev parent reply other threads:[~2007-02-27 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 12:31 Worrisome bug trend Junio C Hamano
2007-02-27 15:09 ` Randal L. Schwartz
2007-02-27 20:22 ` Junio C Hamano
2007-02-27 20:30 ` Johannes Schindelin
2007-02-27 20:41 ` Alexandre Julliard
2007-02-27 21:30 ` Dmitry V. Levin
2007-03-03 2:28 ` Jakub Narebski
2007-02-27 15:36 ` Andy Parkins
2007-02-27 16:00 ` Linus Torvalds
2007-02-27 20:00 ` Johannes Schindelin
2007-02-27 20:25 ` Sam Vilain
2007-02-27 20:42 ` Junio C Hamano
2007-02-27 20:44 ` Johannes Schindelin
2007-02-27 21:07 ` Robin Rosenberg [this message]
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=200702272207.10453.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.