From: Junio C Hamano <gitster@pobox.com>
To: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
Matthew John Cheetham <mjcheetham@outlook.com>,
Jeff King <peff@peff.net>, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH v3] fsck: snapshot default refs before object walk
Date: Sat, 10 Jan 2026 20:01:54 -0800 [thread overview]
Message-ID: <xmqqldi4re4t.fsf@gitster.g> (raw)
In-Reply-To: <pull.2026.v3.git.1767980953134.gitgitgadget@gmail.com> (Elijah Newren via GitGitGadget's message of "Fri, 09 Jan 2026 17:49:13 +0000")
"Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com> writes:
> fsck: snapshot default refs before object walk
>
> Changes in v3:
>
> * Removed the attribution for Matthew, as per his request.
>
> Changes in v2, thanks to feedback & help from Peff & Junio:
>
> * Fixed errors in commit message
> * Changed to use a refname, oid struct and have an array of those
> * Snapshot command line arguments and worktree HEADs too
> * Add TODO items for snapshotting index entries, and for possibly
> improved reflog handling
> * Since nothing from Matthew's original patch in GitHub's fork of git
> remains in this patch by v2 (only a little of it remained in v1), I
> changed authorship to myself and gave Matthew an
> Originally-based-on-a-patch-by trailer.
Thanks. Let's mark it for 'next'.
next prev parent reply other threads:[~2026-01-11 4:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 19:12 [PATCH] fsck: snapshot default refs before object walk Elijah Newren via GitGitGadget
2025-12-30 0:45 ` Junio C Hamano
2026-01-06 23:19 ` Elijah Newren
2026-01-09 13:11 ` Matthew John Cheetham
2026-01-02 5:49 ` Jeff King
2026-01-06 23:36 ` Elijah Newren
2026-01-14 22:23 ` Jeff King
2026-01-07 1:29 ` [PATCH v2] " Elijah Newren via GitGitGadget
2026-01-09 17:49 ` [PATCH v3] " Elijah Newren via GitGitGadget
2026-01-11 4:01 ` Junio C Hamano [this message]
2026-01-14 22:34 ` Jeff King
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=xmqqldi4re4t.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mjcheetham@outlook.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
/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.