From: Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: Brandon Williams <firstname.lastname@example.org>, Duy Nguyen <email@example.com>, "brian m. carlson" <firstname.lastname@example.org>, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, Jeff King <email@example.com>, Git Mailing List <firstname.lastname@example.org> Subject: Re: Add configuration options for some commonly used command-line options Date: Mon, 20 Mar 2017 22:57:03 +0100 Message-ID: <CACBZZX59KXPOEjiUKtZLN6zjO_xpiWve7Xga6q-53J2LwvfZyw@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Mon, Mar 20, 2017 at 7:56 PM, Junio C Hamano <firstname.lastname@example.org> 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 very much doubt this describes anything but a tiny number of cases where people are using the porcelain as an API. People aren't going through the process of trying to find out how to do something with a plumbing command, and then failing and falling back to a porcelain command because the plumbing isn't complete enough. They just use the porcelain because they're familiar with it and scripting it works for them. E.g. I just looked at both major Emacs modes for git now, magit & vc-git, neither use "mktag", they just shell out to "git tag" for making tags. I just went to the git-scm.com website and looked at one open source GUI client I could "git clone", Giggle. It just shells out to e.g. "git commit" to make commits, not "git commit-tree". The other commands they're using are porcelain too. If they've used some plumbing it's probably by sheer accident. E.g. they use ls-tree which is plumbing, but don't use for-each-ref. What's that Google SRE-ism again? Something like "People use the reliability you provide them with in practice, not what you advertise". Our porcelain is very stable, and so people use it as a stable API, and not just for trivial scripts. Which I think has some big implications for how we maintain the porcelain & plumbing. Since people *will* use the porcelain, probably no matter what we advertise to them or how good the plumbing is.
next prev parent reply index Thread overview: 17+ 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 2017-03-20 21:57 ` Ævar Arnfjörð Bjarmason [this message] 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-25 21:28 ` 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 publically 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=CACBZZX59KXPOEjiUKtZLN6zjO_xpiWve7Xga6q-53J2LwvfZyw@mail.gmail.com \ --email@example.com \ --cc=Matthieu.Moy@grenoble-inp.fr \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox