From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] diff: allow turning on textconv explicitly for plumbing
Date: Sun, 07 Dec 2008 19:55:12 -0800 [thread overview]
Message-ID: <7vfxkz9v8f.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081208025700.GB22072@coredump.intra.peff.net> (Jeff King's message of "Sun, 7 Dec 2008 21:57:01 -0500")
Jeff King <peff@peff.net> writes:
> I know this is not strictly a bugfix and we are in -rc, but:
>
> 1. It is an enhancement to a previously unreleased feature, and
> shouldn't affect anything outside of that.
>
> 2. It affects the scripting interface to textconv, so I would like to
> get it in before textconv is ever released so that it is always the
> "right way" to turn text conversion off or on.
I'd agree with #1, especially if you said "doesn't" instead of
"shouldn't".
But I am not 100% sure if the scripting part is "the right way".
If a script wants to take whatever Porcelain users are happy as the
"presentation for human consumption" and pass that through as its own
output to the end user, maybe it is better off reading from Porcelain,
instead of reading from the plumbing (the latter of which requires making
the plumbing output less reliable)?
When we later enhance textconv output from the "diff" Porcelain to benefit
interactive users, it will automatically help the script that passes
through the "diff" output to the end users.
You can certainly argue that this "textconv" feature that is grafted from
Porcelain into plumbing is a special case in that its output is subject to
change any time to help human consumption and we never strive for its
stability as we do for other features in the plumbing to support machine
readability by scripts. You can propagate the later enhancement of
textconv diff output we'd make for Porcelain to the scripted users that
reads from the plumbing that way.
But then wouldn't it be the same for these scripts that do value the
"presentation meant for human consumption" over "machine readability" to
read from Porcelain? That would not have to blur the distinction between
the Porcelain and plumbing like the approach you are suggesting here.
next prev parent reply other threads:[~2008-12-08 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 2:57 [PATCH 2/3] diff: allow turning on textconv explicitly for plumbing Jeff King
2008-12-08 3:55 ` Junio C Hamano [this message]
2008-12-08 4:08 ` Junio C Hamano
2008-12-08 4:59 ` Jeff King
2008-12-08 6:52 ` Junio C Hamano
2008-12-08 7:14 ` Jeff King
2008-12-08 8:27 ` Junio C Hamano
2008-12-09 5:48 ` Jeff King
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=7vfxkz9v8f.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).