From: Johannes Sixt <J.Sixt@eudaptics.com>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Teach 'diff' about 'nodiff' attribute.
Date: Fri, 13 Apr 2007 13:45:56 +0200 [thread overview]
Message-ID: <461F6D74.63EF2769@eudaptics.com> (raw)
In-Reply-To: 200704131230.41594.andyparkins@gmail.com
Andy Parkins wrote:
> I, personally, wouldn't like to say which is correct in that case - or
> in the "nodiff"/"!diff" question. However, I don't think it's correct
> to universally rule out all double negative use - they have their
> place.
Yet in Junio's introductory message, the example was
* crlf !nodiff
and it made me think: huh? And then again: huh?
I don't mind if you call me dumb now, but even an intelligent person
will have to think a second or two about the meaning. That's plainly not
necessary. In particular, where there can be no difference between
"diff" and "!nodiff".
-- Hannes
next prev parent reply other threads:[~2007-04-13 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 9:01 [PATCH 3/3] Teach 'diff' about 'nodiff' attribute Junio C Hamano
2007-04-13 10:49 ` Johannes Sixt
2007-04-13 11:30 ` Andy Parkins
2007-04-13 11:45 ` Johannes Sixt [this message]
2007-04-13 12:54 ` Andy Parkins
2007-04-13 14:09 ` Nicolas Pitre
2007-04-13 14:26 ` Julian Phillips
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=461F6D74.63EF2769@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox