From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Brandon Williams" <bmwill@google.com>,
"Duy Nguyen" <pclouds@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Add configuration options for some commonly used command-line options
Date: Mon, 20 Mar 2017 15:14:03 -0400 [thread overview]
Message-ID: <20170320191403.wn65gyoime2lrubu@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq7f3jwzdo.fsf@gitster.mtv.corp.google.com>
On Mon, Mar 20, 2017 at 11:56:35AM -0700, Junio C Hamano wrote:
> One thing we may want to consider is why we have to even worry about
> scripts getting broken. It is because people script around
> Porcelain, and that is because we have been too eager to improve
> Porcelain while neglecting plumbing for too long, to the point that
> some things are only doable with Porcelain (or doing the same with
> plumbing while possible are made too cumbersome). I find it quite
> disturbing that nobody brought that up as an issue that needs to be
> addressed in this entire thread.
I think there is a chicken-and-egg problem there. The plumbing _wasn't_
there, so people started using porcelain in their scripts, which made us
hesitant to change it. That fact that it doesn't break makes script
writers think it's OK. And now we're stuck with things like "log" and
"diff" as pseudo-plumbing, unless we want to take a strong stand and say
"you're doing it wrong, even though there was no other way to do it
until now".
Unless you want to follow the usual deprecation schedule by introducing
new plumbing commands to fill in the gaps, waiting, and then proceeding
to change the porcelain. But I think that's isomorphic with the other
solutions. I.e., out of:
1. git rev-list
2. GIT_PLUMBING=1 git log
3. git command log
They are all doing the exact same thing: running a log-like command
without any config or cross-version changes. It's just a matter of
syntax. One of the nice things about (2) and (3) is that you don't have
to invent a new plumbing-ish name for each command.
-Peff
next prev parent reply other threads:[~2017-03-20 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 9:57 Add configuration options for some commonly used command-line options (Was: [RFH] GSoC 2015 application) Duy Nguyen
2017-03-19 10:15 ` Add configuration options for some commonly used command-line options Matthieu Moy
2017-03-19 13:18 ` brian m. carlson
2017-03-19 13:43 ` Ævar Arnfjörð Bjarmason
2017-03-20 10:56 ` Duy Nguyen
2017-03-20 17:32 ` Brandon Williams
2017-03-20 18:18 ` Jeff King
2017-03-31 19:44 ` Brandon McCaig
2017-03-20 18:56 ` Junio C Hamano
2017-03-20 19:14 ` Jeff King [this message]
2017-03-20 21:57 ` Ævar Arnfjörð Bjarmason
2017-03-24 23:10 ` [PATCH/RFC] parse-options: add facility to make options configurable Ævar Arnfjörð Bjarmason
2017-03-25 16:47 ` Ævar Arnfjörð Bjarmason
2017-03-25 21:31 ` Jeff King
2017-03-25 22:32 ` Ævar Arnfjörð Bjarmason
2017-03-28 5:17 ` Jeff King
2017-03-28 13:13 ` [PATCH/RFC v2] WIP configurable options facility Ævar Arnfjörð Bjarmason
2017-03-25 21:28 ` [PATCH/RFC] parse-options: add facility to make options configurable brian m. carlson
2017-03-20 10:42 ` Add configuration options for some commonly used command-line options Duy Nguyen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170320191403.wn65gyoime2lrubu@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=sandals@crustytoothpaste.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).