From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH v2] Revert "doc: move git-cherry to plumbing"
Date: Tue, 14 Jan 2025 11:24:53 +0100 [thread overview]
Message-ID: <b0a3889a-9d7f-4663-bb00-b1b457931fcb@app.fastmail.com> (raw)
In-Reply-To: <xmqqv7uiac0m.fsf@gitster.g>
On Mon, Jan 13, 2025, at 17:56, Junio C Hamano wrote:
> kristofferhaugsbakk@fastmail•com writes:
>> This command might only be considered plumbing by way of the plumbing
>> contract that says that plumbing commands have stable output. But
>> hopefully listing this command as Porcelain does not give the impression
>> that the output is not stable. Output stability was in any case not the
>> motivation for moving this command to plumbing.
>
> I do not follow the above reasoning at all.
>
> It is not like it is a crime to intarctively make use of a plumbing
> command, or we intentionally try to hide plumbing command from them
> by making it deliberately less accessible. "git cat-file commit X"
> may be handier than "git show -s X" for some people and that is not
> to be frowned upon.
>
> And what you call "might only be" is really the crucial thing to
> consider. If we want to keep a tool's output stable and machine
> readable, we need to mark it as "meant for Porcelain writers", and
> classifying the tool as plumbing is a pretty much established way to
> do so.
Okay. I understand now.
--
Kristoffer
next prev parent reply other threads:[~2025-01-14 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 11:54 [PATCH v2] Revert "doc: move git-cherry to plumbing" kristofferhaugsbakk
2025-01-12 12:30 ` Kristoffer Haugsbakk
2025-01-13 16:56 ` Junio C Hamano
2025-01-14 10:24 ` Kristoffer Haugsbakk [this message]
2025-01-14 17:35 ` Junio C Hamano
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=b0a3889a-9d7f-4663-bb00-b1b457931fcb@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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