All of lore.kernel.org
 help / color / mirror / Atom feed
From: shejialuo <shejialuo@gmail.com>
To: Patrick Steinhardt <ps@pks.im>, a@archlinux
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org,
	Christian Couder <christian.couder@gmail.com>,
	Derrick Stolee <stolee@gmail.com>
Subject: Re: What's cooking in git.git (Nov 2024, #07; Wed, 20)
Date: Wed, 20 Nov 2024 21:41:17 +0800	[thread overview]
Message-ID: <Zz3m_aKFz1s9DAg1@ArchLinux> (raw)
In-Reply-To: <Zz27kX159PKAmBOb@pks.im>

On Wed, Nov 20, 2024 at 11:36:10AM +0100, Patrick Steinhardt wrote:
> > * sj/ref-contents-check (2024-11-15) 9 commits
> >  - ref: add symlink ref content check for files backend
> >  - ref: check whether the target of the symref is a ref
> >  - ref: add basic symref content check for files backend
> >  - ref: add more strict checks for regular refs
> >  - ref: port git-fsck(1) regular refs check for files backend
> >  - ref: support multiple worktrees check for refs
> >  - ref: initialize ref name outside of check functions
> >  - ref: check the full refname instead of basename
> >  - 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).
> > 
> >  Comments?
> >  source: <ZzYqoai8X_Wdtbmt@ArchLinux>
> 
> I've already reviewed this version and expect a (probably final) reroll.
> 

I have already being waiting a couple of days for more comments. And I
have submitted a new version just now.

Thanks,
Jialuo

  reply	other threads:[~2024-11-20 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  8:49 What's cooking in git.git (Nov 2024, #07; Wed, 20) Junio C Hamano
2024-11-20 10:36 ` Patrick Steinhardt
2024-11-20 13:41   ` shejialuo [this message]
2024-11-21  1:10   ` Junio C Hamano
2024-11-20 10:39 ` karthik nayak
2024-11-20 16:40 ` Taylor Blau
2024-11-21  0:44   ` Junio C Hamano
2024-11-22  4:34   ` Junio C Hamano
2024-11-21  8:26 ` Kristoffer Haugsbakk
2024-11-21 12:59   ` Junio C Hamano
2024-11-21 15:31     ` Kristoffer Haugsbakk
2024-11-21 23:11       ` 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=Zz3m_aKFz1s9DAg1@ArchLinux \
    --to=shejialuo@gmail.com \
    --cc=a@archlinux \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    --cc=stolee@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.