From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Johannes Sixt <j6t@kdbg.org>, Duy Nguyen <pclouds@gmail.com>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: is there a reason pre-commit.sample uses "git diff-index"?
Date: Fri, 01 Jun 2018 11:23:49 +0900 [thread overview]
Message-ID: <xmqqh8mn9rd6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGZ79kZ9x2OWU+qfZRckZFAdy1KFqttAZqkJwbzsvQfqUokg3A@mail.gmail.com> (Stefan Beller's message of "Thu, 31 May 2018 16:25:04 -0700")
Stefan Beller <sbeller@google.com> writes:
> plumbing command, so the likelihood of git-log calls in scripts out
> there is high.
>
> So maybe the community should strive to be more aggressive about
> changing the porcelain interface for the better.
To me, these two paragraphs are being incoherent.
If plumbing these days lag behind "log" Porcelain and tempt script
writers more towards "log", we should aggressively reject attempts
to change the "log" Porcelain behaviour to keep it stable, until a
suitable plumbing that scripters can rely on catches up.
Or course, aggressively improving plumbing would be a good solution
to that problem as well ;-)
prev parent reply other threads:[~2018-06-01 2:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 16:38 is there a reason pre-commit.sample uses "git diff-index"? Robert P. J. Day
2018-05-31 17:05 ` Duy Nguyen
2018-05-31 17:27 ` Robert P. J. Day
2018-05-31 17:41 ` Duy Nguyen
2018-05-31 23:08 ` Johannes Sixt
2018-05-31 23:09 ` Robert P. J. Day
2018-05-31 23:25 ` Stefan Beller
2018-06-01 2:23 ` Junio C Hamano [this message]
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=xmqqh8mn9rd6.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=pclouds@gmail.com \
--cc=rpjday@crashcourse.ca \
--cc=sbeller@google.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