All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marius Storm-Olsen <marius@trolltech.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: "Wincent Colaiuta" <win@wincent.com>,
	"David Kastrup" <dak@gnu.org>,
	"René Scharfe" <rene.scharfe@lsrfire.ath.cx>,
	"Junio Hamano" <junkio@cox.net>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH 0/7] Bisect dunno
Date: Sun, 14 Oct 2007 19:24:12 +0200	[thread overview]
Message-ID: <471250BC.7070307@trolltech.com> (raw)
In-Reply-To: <522E90CF-FC15-472F-B0A8-91C310CAF9BF@wincent.com>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

Wincent Colaiuta said the following on 14.10.2007 18:35:
> El 14/10/2007, a las 18:25, David Kastrup escribió:
>> René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
>> 
>>> Christian Couder schrieb:
>>>> I choosed "dunno" because that was what Dscho suggested in
>>>> this thread:
>>>> 
>>>> http://thread.gmane.org/gmane.comp.version-control.git/53584/
>>>>  focus=53595
>>>> 
>>>> It seems to me short and understandable at the same time.
>>>> 
>>>> More meaningfull would be "untestable" or "cannottest" or 
>>>> "canttest" but it's much longer, while "good" and "bad" are
>>>> short.
>>> Ugly?  Neutral?
>> "Ugly" has a certain charm to it but would probably not translate
>>  well.  "Limbo" would be another such candidate, probably with
>> better translatability.  But while some of those have some geeky
>> appeal, I really think something reasonably plain like
>> "undecided" would be better in the long run.
> 
> "undecided" sounds good to me. It should be clear to non-native 
> speakers of English (at least, clearer than "dunno").

What about just "unknown"?

-- 
.marius


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

  reply	other threads:[~2007-10-14 17:24 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 [this message]
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
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=471250BC.7070307@trolltech.com \
    --to=marius@trolltech.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=rene.scharfe@lsrfire.ath.cx \
    --cc=win@wincent.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 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.