From: David Kastrup <dak@gnu•org>
To: "David Symonds" <dsymonds@gmail•com>
Cc: "Geert Bosch" <bosch@adacore•com>,
"Wincent Colaiuta" <win@wincent•com>,
"Johan Herland" <johan@herland•net>,
git@vger•kernel.org, "Marius Storm-Olsen" <marius@trolltech•com>,
"Christian Couder" <chriscool@tuxfamily•org>,
"René Scharfe" <rene.scharfe@lsrfire•ath.cx>,
"Junio Hamano" <junkio@cox•net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx•de>
Subject: Re: [PATCH 0/7] Bisect dunno
Date: Tue, 16 Oct 2007 08:17:16 +0200 [thread overview]
Message-ID: <856417h9cj.fsf@lola.goethe.zz> (raw)
In-Reply-To: <ee77f5c20710152307n48431a6eu5dc95ee504968e4e@mail.gmail.com> (David Symonds's message of "Tue\, 16 Oct 2007 16\:07\:58 +1000")
"David Symonds" <dsymonds@gmail•com> writes:
> On 16/10/2007, David Kastrup <dak@gnu•org> wrote:
>> Geert Bosch <bosch@adacore•com> writes:
>>
>> > On Oct 15, 2007, at 13:53, David Symonds wrote:
>> >> That's also why I suggested "skip"; you might not be able to test a
>> >> particular commit, but you might also not *want* to test a particular
>> >> commit for some reason.
>> >
>> > Skip seems a great choice: it directly expresses the wish to
>> > not consider a certain commit. The reason is unimportant.
>>
>> But it is an _action_, while "good" and "bad" are properties.
>
> "skipped", then.
"good" and "bad" are descriptive. "to be skipped" would be necessary
to fit it.
> Either way, something like this has got to be much better than
> "dunno".
"undecided" still has my vote, and I could live with "unknown".
Everything that has been proposed since then is, in my opinion,
strictly worse.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-10-16 6:16 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=856417h9cj.fsf@lola.goethe.zz \
--to=dak@gnu$(echo .)org \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=bosch@adacore$(echo .)com \
--cc=chriscool@tuxfamily$(echo .)org \
--cc=dsymonds@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=johan@herland$(echo .)net \
--cc=junkio@cox$(echo .)net \
--cc=marius@trolltech$(echo .)com \
--cc=rene.scharfe@lsrfire$(echo .)ath.cx \
--cc=win@wincent$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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