From: Junio C Hamano <gitster@pobox.com>
To: Keith Cascio <keith@CS.UCLA.EDU>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC v1 1/1] +5 cases (4 fail), diff whitespace tests
Date: Sat, 17 Jan 2009 23:47:02 -0800 [thread overview]
Message-ID: <7vd4elys21.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.GSO.2.00.0901141633030.9831@kiwi.cs.ucla.edu> (Keith Cascio's message of "Wed, 14 Jan 2009 16:48:24 -0800 (PST)")
Keith Cascio <keith@CS.UCLA.EDU> writes:
> +5 cases (4 fail), diff whitespace tests
> There are 2^3 = eight possible combinations of the three flags:
> -w -b --ignore-space-at-eol
> Three of those combinations were already being tested:
> [none]
> -w
> -b
> Add tests of the other five combinations,
Hmm. Are these three supposed to be orthogonal?
next prev parent reply other threads:[~2009-01-18 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 0:48 [PATCH/RFC v1 1/1] +5 cases (4 fail), diff whitespace tests Keith Cascio
2009-01-18 7:45 ` Junio C Hamano
2009-01-18 7:47 ` Junio C Hamano [this message]
2009-01-18 19:25 ` Keith Cascio
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=7vd4elys21.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=keith@CS.UCLA.EDU \
/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;
as well as URLs for NNTP newsgroup(s).