git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Martin Ågren" <martin.agren@gmail.com>,
	"Teng Long" <dyroneteng@gmail.com>
Subject: Re: [PATCH] ls-tree doc: document interaction with submodules
Date: Fri, 08 Apr 2022 11:20:31 -0700	[thread overview]
Message-ID: <xmqqpmlrmo7k.fsf@gitster.g> (raw)
In-Reply-To: <patch-1.1-183b9639ae7-20220408T155704Z-avarab@gmail.com> ("Ævar	Arnfjörð Bjarmason"'s message of "Fri, 8 Apr 2022 18:00:25 +0200")

Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:

> Thanks, perhaps this is also worth taking before the release, it's a
> rather trivial inaccuracy in the docs, but something that's new since
> v2.36.0.
> ...
> diff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt
> index 8f31e2ee9d4..0240adb8eec 100644
> --- a/Documentation/git-ls-tree.txt
> +++ b/Documentation/git-ls-tree.txt
> @@ -151,11 +151,11 @@ names can be used:
>  objectmode::
>  	The mode of the object.
>  objecttype::
> -	The type of the object (`blob` or `tree`).
> +	The type of the object (`commit`, `blob` or `tree`).
>  objectname::
>  	The name of the object.
>  objectsize[:padded]::
> -	The size of the object ("-" if it's a tree).
> +	The size of a `blob` object ("-" if it's a `commit` or `tree`).
>  	It also supports a padded format of size with "%(objectsize:padded)".
>  path::
>  	The pathname of the object.

Makes sense.  Indeed we should have updated it when we added
gitlinks to trees.

Will queue.

      reply	other threads:[~2022-04-08 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 15:52 [PATCH] git-ls-tree.txt: fix the name of "%(objectsize:padded)" Martin Ågren
2022-04-07 17:11 ` Junio C Hamano
2022-04-08 16:00 ` [PATCH] ls-tree doc: document interaction with submodules Ævar Arnfjörð Bjarmason
2022-04-08 18:20   ` 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=xmqqpmlrmo7k.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=dyroneteng@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=martin.agren@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;
as well as URLs for NNTP newsgroup(s).