All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: ZheNing Hu <adlternative@gmail.com>
Cc: "ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com>,
	"Git List" <git@vger.kernel.org>,
	"Christian Couder" <christian.couder@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v2] ls-files.c: add --object-only option
Date: Mon, 13 Jun 2022 10:19:12 -0700	[thread overview]
Message-ID: <xmqqwndk7a7j.fsf@gitster.g> (raw)
In-Reply-To: <CAOLTT8SNOYYVmk3fvEc=Vp9MuRp+1H--wh72rP=ORRtffonUfQ@mail.gmail.com> (ZheNing Hu's message of "Sun, 12 Jun 2022 18:24:26 +0800")

ZheNing Hu <adlternative@gmail.com> writes:

> I think those atoms are undoubtedly necessary to keep
>
> %(tag)
> %(objectmode)
> %(objectname)
> %(stage)
> %(path)

I am not sure what you mean by "keep".  You cannot keep what you do
not have yet ;-)

If ls-files needs (that is a big if; it is a plumbing to be used by
whatever program that want to assemble the pieces, and it shouldn't
have to learn such assembly itself) to support "--format", so that
people can reinvent its "-s" output (but why?  There already is "-s"
output available), then the above would be necessary (assuming that
via the "--format" the user will be able to supply inter-field
spaces and tabs properly).  I do not know if there are other things
available in output other than the "-s" option produces offhand, but
if there are, they would need to be added for completeness.

      reply	other threads:[~2022-06-13 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 10:01 [PATCH] ls-files.c: add --only-object-name option ZheNing Hu via GitGitGadget
2022-06-06 17:42 ` Ævar Arnfjörð Bjarmason
2022-06-08 14:38   ` ZheNing Hu
2022-06-08 16:09     ` Junio C Hamano
2022-06-09 12:37 ` [PATCH v2] ls-files.c: add --object-only option ZheNing Hu via GitGitGadget
2022-06-09 19:50   ` Junio C Hamano
2022-06-12 10:24     ` ZheNing Hu
2022-06-13 17:19       ` Junio C Hamano [this message]

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=xmqqwndk7a7j.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=adlternative@gmail.com \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.