From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Junio Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH 0/7] Bisect dunno
Date: Wed, 17 Oct 2007 19:10:37 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710171906280.25221@racer.site> (raw)
In-Reply-To: <20071017073538.GB13801@spearce.org>
Hi,
On Wed, 17 Oct 2007, Shawn O. Pearce wrote:
> Christian Couder <chriscool@tuxfamily.org> wrote:
> > Here is my bisect dunno patch series again.
> > The changes since last time are the following:
>
> I now have this series queued in my pu branch. It passes the tests
> it comes with, and doesn't appear to break anything, but apparently
> there is also still some debate about what a dunno should be called
> ("unknown", "void", "ugly", "dunno", "skip" ...).
AFAICT these are all bikeshed painting arguments, not technical arguments.
I was initially opposed to having --bisect-all, wanting to have
--bisect-dunno <ref>...
But in the end, the people doing the work decide, and therefore I am fine
with --bisect-all, especially since it seems clean enough for me.
As for all those "dunno is no English"... I'd first merge the technical
part (i.e. what you have now in pu), and then let the discussion about
which synonyms to choose continue, until a consensus is formed about other
names (if there is a consensus at all!).
IMHO there is no reason to hold of the fine work of Christian, just
because there are non-technical arguments still in the air.
I want bisect dunno. Even if there is another name later.
Ciao,
Dscho
next prev parent reply other threads:[~2007-10-17 18:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 12:28 [PATCH 0/7] Bisect dunno Christian Couder
2007-10-14 12:43 ` Wincent Colaiuta
2007-10-14 12:59 ` Wincent Colaiuta
2007-10-14 13:00 ` David Kastrup
2007-10-14 15:09 ` Christian Couder
2007-10-14 15:09 ` David Kastrup
2007-10-14 15:14 ` Andreas Ericsson
2007-10-14 16:13 ` René Scharfe
2007-10-14 16:25 ` David Kastrup
2007-10-14 16:35 ` Wincent Colaiuta
2007-10-14 17:24 ` Marius Storm-Olsen
2007-10-14 17:48 ` David Kastrup
2007-10-15 6:04 ` Marius Storm-Olsen
2007-10-15 6:15 ` David Symonds
2007-10-15 7:02 ` Johan Herland
2007-10-15 9:31 ` Wincent Colaiuta
2007-10-15 11:53 ` David Symonds
2007-10-15 20:33 ` Geert Bosch
2007-10-15 20:47 ` David Kastrup
2007-10-16 6:07 ` David Symonds
2007-10-16 6:17 ` David Kastrup
2007-10-17 16:10 ` Robin Rosenberg
2007-10-17 16:13 ` David Kastrup
2007-10-17 16:17 ` Karl Hasselström
2007-10-17 19:23 ` Karl Hasselström
2007-10-17 22:59 ` Linus Torvalds
2007-10-17 23:46 ` Johannes Schindelin
2007-10-17 23:59 ` Linus Torvalds
2007-10-18 1:24 ` David Symonds
[not found] ` <200710190449.49477.chriscool@tuxfamily.org>
2007-10-19 2:49 ` Shawn O. Pearce
2007-10-16 3:41 ` Christian Couder
2007-10-15 8:25 ` David Kastrup
2007-10-14 17:25 ` Johannes Schindelin
2007-10-14 16:16 ` Johannes Schindelin
2007-10-17 7:35 ` Shawn O. Pearce
2007-10-17 18:10 ` Johannes Schindelin [this message]
2007-10-17 23:36 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0710171906280.25221@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).