public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Cc: valusoutrik@gmail.com,  ayu.chandekar@gmail.com,
	 git@vger.kernel.org, jltobler@gmail.com,  karthik.188@gmail.com,
	 lucasseikioshiro@gmail.com, siddharthasthana31@gmail.com
Subject: Re: [RFC RFC PATCH] builtin/repo.c: change info default behavior to show all fields
Date: Tue, 24 Feb 2026 18:44:53 -0800	[thread overview]
Message-ID: <xmqqjyw1cziy.fsf@gitster.g> (raw)
In-Reply-To: <20260225001439.54954-1-jayatheerthkulkarni2005@gmail.com> (K. Jayatheerth's message of "Wed, 25 Feb 2026 05:44:39 +0530")

K Jayatheerth <jayatheerthkulkarni2005@gmail.com> writes:

>>> They do not matter plumbing commands intended to be used in scripts.
>>> What matters more is being predictable.
>
>> My bad for this ... I did not know about plumbing commands.
>
> In the Pro Git book there is a chapter which has a very good description of
> plumbing vs porcelain [1]. It might help.
>
>>> And it is more predictable.  If you ask for two things, you get two
>>> things.  If you ask for one thing, you get one thing.  If you ask
>>> for zero things?  You get none.
>
>> Got it.
>> Thanks for the clarification.
>
> [1] https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain
>
> Regards,
> Jayatheerth

Thanks for clarifying what I left unsaid.  Very much appreciated.

  reply	other threads:[~2026-02-25  2:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 20:40 [RFC RFC PATCH] builtin/repo.c: change info default behavior to show all fields SoutrikDas
2026-02-24 21:03 ` [PATCH v2] " SoutrikDas
2026-02-24 21:23 ` [RFC RFC PATCH] " Junio C Hamano
2026-02-24 22:08   ` SoutrikDas
2026-02-25  0:14     ` K Jayatheerth
2026-02-25  2:44       ` Junio C Hamano [this message]
2026-02-25 15:34         ` SoutrikDas
2026-02-25 15:46           ` Junio C Hamano
2026-02-25 15:48           ` Kristoffer Haugsbakk
2026-02-25 17:02           ` JAYATHEERTH K
2026-02-25 15:11       ` Lucas Seiki Oshiro
2026-02-25 15:38         ` SoutrikDas
2026-02-25 15:31       ` SoutrikDas
2026-02-25 16:08         ` Lucas Seiki Oshiro

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=xmqqjyw1cziy.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jayatheerthkulkarni2005@gmail.com \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=lucasseikioshiro@gmail.com \
    --cc=siddharthasthana31@gmail.com \
    --cc=valusoutrik@gmail.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