From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Josh Soref" <gitgitgadget@gmail.com>,
git@vger.kernel.org,
"Daniele Sassoli" <danielesassoli@gmail.com>
Subject: Re: [PATCH] Document count-objects pack
Date: Thu, 14 Aug 2025 07:46:44 -0700 [thread overview]
Message-ID: <xmqqwm766jvv.fsf@gitster.g> (raw)
In-Reply-To: <8147cec2-f898-40d7-ac3b-763920eb7947@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 14 Aug 2025 09:30:51 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Wed, Aug 13, 2025, at 11:40, Daniele Sassoli via GitGitGadget wrote:
>> From: Daniele Sassoli <danielesassoli@gmail.com>
>>
>> Juno added the printing of "packs" with ae72f685418b.
>> When 0bdaa1216 refactored the docs for the -v option, this was missed.
>
> s/Juno/Junio/
>
> But commits are usually just listed as-is without mentioning authors or
> other metadata. Something like this:[1]
>
> ae72f685418 (count-objects -v: show number of packs as well.,
> 2006-12-27) added `packs` to the output of `-v`. 0bdaa12169b
> (git-count-objects.txt: describe each line in -v output, 2013-02-08)
> forgot to include `packs`.
>
> The text above is a bit more terse around the commit references since
> the subject line for the second commit says what the intent was.
>
> Alternatively, just referencing the second commit:
>
> 0bdaa12169b (git-count-objects.txt: describe each line in -v output,
> 2013-02-08) forgot to include `packs`.
Thanks.
next prev parent reply other threads:[~2025-08-14 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 9:40 [PATCH] Document count-objects pack Daniele Sassoli via GitGitGadget
2025-08-14 7:30 ` Kristoffer Haugsbakk
2025-08-14 14:46 ` Junio C Hamano [this message]
2025-08-14 13:16 ` [PATCH v2] " Daniele Sassoli via GitGitGadget
2025-08-14 13:46 ` Kristoffer Haugsbakk
2025-08-14 14:33 ` [PATCH v3] count-objects: document " Daniele Sassoli via GitGitGadget
2025-08-14 21:40 ` 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=xmqqwm766jvv.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=danielesassoli@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=kristofferhaugsbakk@fastmail.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).