git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karthik Nayak <karthik.188@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, shejialuo <shejialuo@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: What's cooking in git.git (Feb 2025, #09; Fri, 28)
Date: Fri, 7 Mar 2025 02:48:55 -0800	[thread overview]
Message-ID: <CAOLa=ZSe01-ziQi5SB+aZX8rtA7ZtzgapW7nH7+afO2yKPDaaQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqldtmvyfa.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]

Junio C Hamano <gitster@pobox.com> writes:

> shejialuo <shejialuo@gmail.com> writes:
>
>> On Fri, Feb 28, 2025 at 04:45:31PM -0800, Junio C Hamano wrote:
>>
>>> * sj/ref-consistency-checks-more (2025-02-27) 9 commits
>>>  - builtin/fsck: add `git refs verify` child process
>>>  - packed-backend: check whether the "packed-refs" is sorted
>>>  - packed-backend: add "packed-refs" entry consistency check
>>>  - packed-backend: check whether the refname contains NUL characters
>>>  - packed-backend: add "packed-refs" header consistency check
>>>  - packed-backend: check if header starts with "# pack-refs with: "
>>>  - packed-backend: check whether the "packed-refs" is regular file
>>>  - builtin/refs: get worktrees without reading head information
>>>  - t0602: use subshell to ensure working directory unchanged
>>>
>>>  "git fsck" becomes more careful when checking the refs.
>>>
>>>  Comments?
>>>  source: <Z8CMx7O19PMs9sVY@ArchLinux>
>>
>> I think I have addressed the comments from you, Patrick and Karthik.
>> Could we make the patch into "next"?
>
> Mine was merely a small kibitzing on the logic flow structure, and I
> didn't really looked at the larger picture beyond that part of the
> code I looked at.  Let's hear from Patrick and Karthik (cc'ed) if
> they find the result of the updates satisfactory.
>

Sorry I missed this email. I did review an earlier version of the series
and it did look good to me, haven't reviewed the latest version (but
that's not a blocker from my side).

> Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]

  parent reply	other threads:[~2025-03-07 10:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-01  0:45 What's cooking in git.git (Feb 2025, #09; Fri, 28) Junio C Hamano
2025-03-03 15:24 ` shejialuo
2025-03-03 17:03   ` Junio C Hamano
2025-03-04  6:27     ` Patrick Steinhardt
2025-03-04 12:25       ` shejialuo
2025-03-04 15:30       ` Junio C Hamano
2025-03-07 10:48     ` Karthik Nayak [this message]
2025-03-04  6:31 ` Patrick Steinhardt
2025-03-04  7:02   ` ps/reftable-sans-compat-util, was " Johannes Schindelin
2025-03-04  7:40     ` Johannes Schindelin
2025-03-04  9:46       ` Patrick Steinhardt
2025-03-04 10:06         ` Patrick Steinhardt
2025-03-26 16:57           ` Johannes Schindelin
2025-03-27 15:28             ` Junio C Hamano
2025-03-28  5:36               ` Patrick Steinhardt
2025-03-28 15:31                 ` Johannes Schindelin
2025-03-30  0:56                   ` Junio C Hamano
2025-03-29 23:56                 ` 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='CAOLa=ZSe01-ziQi5SB+aZX8rtA7ZtzgapW7nH7+afO2yKPDaaQ@mail.gmail.com' \
    --to=karthik.188@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    --cc=shejialuo@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).