From: Junio C Hamano <gitster@pobox•com>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: Ian Jackson <ijackson@chiark•greenend.org.uk>, git@vger•kernel.org
Subject: Re: [PATCH 0/5] git check-ref-format --stdin --report-errors
Date: Mon, 19 Dec 2016 10:23:45 -0800 [thread overview]
Message-ID: <xmqqlgvbpyku.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <561c0338-66cd-f806-7b3b-b422f98a1564@alum.mit.edu> (Michael Haggerty's message of "Mon, 19 Dec 2016 12:29:40 +0100")
Michael Haggerty <mhagger@alum•mit.edu> writes:
> Especially given that the output is not especially machine-readable, it
> might be more consistent with other commands to call the new feature
> `--verbose` rather than `--report-errors`.
Don't we instead want to structure the output to be machine-readable
instead, given that check-ref-format is a very low level plumbing
command that is primarily meant for scriptors?
next prev parent reply other threads:[~2016-12-19 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 19:13 [PATCH 0/5] git check-ref-format --stdin --report-errors Ian Jackson
2016-11-04 19:13 ` [PATCH 1/5] check-ref-format: Refactor out check_one_ref_format Ian Jackson
2016-12-19 8:27 ` Michael Haggerty
2016-12-19 13:19 ` Ian Jackson
2016-12-20 6:57 ` Michael Haggerty
2016-11-04 19:13 ` [PATCH 2/5] check-ref-format: Refactor to make --branch code more common Ian Jackson
2016-12-19 11:07 ` Michael Haggerty
2016-12-19 11:54 ` Ian Jackson
2016-11-04 19:13 ` [PATCH 3/5] check-ref-format: Abolish leak of collapsed refname Ian Jackson
2016-12-19 11:09 ` Michael Haggerty
2016-11-04 19:13 ` [PATCH 4/5] check-ref-format: New --report-errors option Ian Jackson
2016-11-04 19:13 ` [PATCH 5/5] check-ref-format: New --stdin option Ian Jackson
2016-12-19 11:22 ` Michael Haggerty
2016-12-19 13:43 ` Michael Haggerty
2016-12-19 11:29 ` [PATCH 0/5] git check-ref-format --stdin --report-errors Michael Haggerty
2016-12-19 16:22 ` Ian Jackson
2016-12-19 18:23 ` Junio C Hamano [this message]
2016-12-20 7:29 ` Michael Haggerty
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=xmqqlgvbpyku.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ijackson@chiark$(echo .)greenend.org.uk \
--cc=mhagger@alum$(echo .)mit.edu \
/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