archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: "Ævar Arnfjörð Bjarmason" <>
Subject: Re: RFC: Modernizing the contept of plumbing v.s. porcelain
Date: Mon, 14 Dec 2020 14:49:44 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (=?utf-8?B?IsOGdmFyIEFy?= =?utf-8?B?bmZqw7Zyw7A=?= Bjarmason"'s message of "Thu, 10 Dec 2020 15:14:58 +0100")

Ævar Arnfjörð Bjarmason <> writes:

> I.e. the existing advice was to say "just use plumbing", now it takes a
> more nuanced view of e.g. pointing out that certin porcelain commands
> have "-z" options that can be considered as reliable as things
> explicitly marked as plumbing.

Yup, and we have --porcelain option to some commands that are meant
to help Porcelain writers.

> It's widespread traditional wisdom when discussing git that there's
> plumbing and porcelain, but I think ever since all the builtins were
> shellscripts way-back-when this distinction has blurred.

Yeah, it is somewhat unfortunate that it is human nature to be
excited by shiny new toys that are end results; some of the newer
features we added and only available at the Porcelain level may be
better made available to the plumbing, but that is one of the
easiest corners authors can cut.

>  2. Either inline at the bottom, or probably better in a new
>     gitplumbing(5) (or gitapi(5) or something) explain the nuance, that
>     some commads are pure-plumbing, some pure-porcelain, and some are
>     hybrids.
>     That you can follow some general rules (does it have "-z" output,
>     can probably be relied on) to determine "plumbing-like", or
>     porcelain-like (is it stdout/stderr output in English, does it
>     change under i18n?), that not all manpages might explicitly call out
>     plumbing / porcelain, and that when in doubt ask the list.


  reply	other threads:[~2020-12-14 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  8:17 RFC: Modernizing the contept of plumbing v.s. porcelain Ævar Arnfjörð Bjarmason
2020-12-09 19:38 ` Junio C Hamano
2020-12-10 14:14   ` Ævar Arnfjörð Bjarmason
2020-12-14 22:49     ` Junio C Hamano [this message]
2020-12-10  3:07 ` Felipe Contreras

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).