From: ZheNing Hu <adlternative@gmail.com>
To: Martin Monperrus <martin.monperrus@gnieh.org>
Cc: git@vger.kernel.org
Subject: Re: bug report git ls-files format
Date: Sat, 13 May 2023 16:39:51 +0800 [thread overview]
Message-ID: <CAOLTT8SvqmsjDRFQeMUjbri7mhp14KRxQqeKUq2jvS93u3Ryeg@mail.gmail.com> (raw)
In-Reply-To: <21183ea9-84e2-fd89-eb9b-419556680c07@gnieh.org>
Martin Monperrus <martin.monperrus@gnieh.org> 于2023年5月13日周六 14:19写道：
>
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> Run `git ls-files . --format="%(objectmode) %(objecttype) %(objectname)%x09%(path)"`
>
> What did you expect to happen? (Expected behavior)
>
> Have the full output per the format specifier
>
> What happened instead? (Actual behavior)
>
> fatal: bad ls-files format: %(objecttype)
>
> What's different between what you expected and what actually happened?
>
> %(objecttype) is not supported. It is supported in git ls-tree. For sake of consistency it would be
> good to have it here.
>
It's not a bug, but completion of the functionality would be better.
In addition to %(objecttype), there may also be %(objectsize), and I will submit
a patch to complete it later.
> Anything else you want to add:
>
> Please review the rest of the bug report below.
> You can delete any lines you don't wish to share.
>
>
> [System Info]
> git version:
> git version 2.40.1
> cpu: x86_64
> no commit associated with this build
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> uname: Linux 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64
> compiler info: gnuc: 12.2
> libc info: glibc: 2.35
> $SHELL (typically, interactive shell): /bin/bash
>
>
> [Enabled Hooks]
> pre-commit
>
Thanks,
ZheNing Hu
prev parent reply other threads:[~2023-05-13 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 5:55 bug report git ls-files format Martin Monperrus
2023-05-13 8:39 ` ZheNing Hu [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=CAOLTT8SvqmsjDRFQeMUjbri7mhp14KRxQqeKUq2jvS93u3Ryeg@mail.gmail.com \
--to=adlternative@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.monperrus@gnieh.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).