From: Adam Spiers <git@adamspiers.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: [PATCH] Improve legibility of test_expect_code output
Date: Thu, 20 Sep 2012 01:48:20 +0100 [thread overview]
Message-ID: <CAOkDyE95x0_ZVCsrsC8kJWdrzMo8b0nQ19N+QKXy64vQ4N6E+A@mail.gmail.com> (raw)
In-Reply-To: <7vy5k5cyzg.fsf@alter.siamese.dyndns.org>
On Thu, Sep 20, 2012 at 1:35 AM, Junio C Hamano <gitster@pobox.com> wrote:
> If it were "..., we wanted 128 from 'git foo bar'", then I would,
> but otherwise, not really.
That's fine by me. Both are better than the status quo.
next prev parent reply other threads:[~2012-09-20 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 22:38 [PATCH] Improve legibility of test_expect_code output Adam Spiers
2012-09-20 0:06 ` Junio C Hamano
2012-09-20 0:25 ` Adam Spiers
2012-09-20 0:35 ` Junio C Hamano
2012-09-20 0:48 ` Adam Spiers [this message]
2012-09-20 16:50 ` Junio C Hamano
2012-09-20 16:57 ` Adam Spiers
2012-09-20 17:45 ` Junio C Hamano
2012-09-20 18:05 ` Adam Spiers
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=CAOkDyE95x0_ZVCsrsC8kJWdrzMo8b0nQ19N+QKXy64vQ4N6E+A@mail.gmail.com \
--to=git@adamspiers.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).