From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Worrisome bug trend
Date: Tue, 27 Feb 2007 07:09:06 -0800 [thread overview]
Message-ID: <86odnfr625.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7vodnfg4sy.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Tue, 27 Feb 2007 04:31:41 -0800")
>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:
Junio> Which is kind of depressing...
Maybe if you looked at who has been reporting the bugs, you'd find a different
story. It's quite possible that the "inner circle" all used git in a
homogeneous way, not performing every possible advertised operation, but now
that git is being used by more people, older bugs are getting revealed because
people really are using it out there in some nicely unique (or perhaps
boneheaded :) ways.
Any quick stats on diversity of bug submitters?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-02-27 15:09 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 [this message]
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
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=86odnfr625.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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.