From: shejialuo <shejialuo@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: What's cooking in git.git (Sep 2024, #02; Sun, 8)
Date: Mon, 9 Sep 2024 22:07:51 +0800 [thread overview]
Message-ID: <Zt8BN7fmYOSaDoeK@ArchLinux.localdomain> (raw)
In-Reply-To: <xmqqed5tv9eu.fsf@gitster.g>
On Sun, Sep 08, 2024 at 07:38:17PM -0700, Junio C Hamano wrote:
> [Cooking]
[snip]
> * sj/ref-contents-check (2024-09-03) 4 commits
> - ref: add symlink ref content check for files backend
> - ref: add symref content check for files backend
> - ref: add regular ref content check for files backend
> - ref: initialize "fsck_ref_report" with zero
>
> "git fsck" learned to issue warnings on "curiously formatted" ref
> contents that have always been taken valid but something Git
> wouldn't have written itself (e.g., missing terminating end-of-line
> after the full object name).
>
> Ready?
> source: <Ztb-mgl50cwGVO8A@ArchLinux>
>
Just a kindly remind here for reviewing. :)
Thanks,
Jialuo
prev parent reply other threads:[~2024-09-09 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 2:38 What's cooking in git.git (Sep 2024, #02; Sun, 8) Junio C Hamano
2024-09-09 14:07 ` shejialuo [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=Zt8BN7fmYOSaDoeK@ArchLinux.localdomain \
--to=shejialuo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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).