All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org, jltobler@gmail.com
Subject: Re: [PATCH v2] builtin/refs: add '--skip-reflog' flag to bypass reflog migration
Date: Tue, 11 Feb 2025 13:21:55 +0100	[thread overview]
Message-ID: <Z6tA4zC4WhdAVbPD@pks.im> (raw)
In-Reply-To: <20250211-477-refs-migrate-add-a-flag-to-ignore-reflogs-during-migration-v2-1-991a2ec9a796@gmail.com>

On Tue, Feb 11, 2025 at 12:42:18PM +0100, Karthik Nayak wrote:
> The 'git-refs(1)' migrate subcommand, which transfers repositories
> between reference backends, currently migrates reflogs by default as of
> 246cebe320 (refs: add support for migrating reflogs, 2024-12-16).
> 
> While this behavior is desirable for most client-side repositories,
> server-side repositories are not expected to contain reflogs. However,
> due to historical reasons, some may still have them. This could be
> caused, for example, by bugs, misconfiguration, or an administrator
> enabling reflogs on the server for debugging purposes.
> 
> To address this, introduce the --skip-reflog flag, allowing users to
> bypass reflog migration. This ensures that the repository ends up in the
> expected state after migration.

Thanks, this version looks good to me.

Patrick

  reply	other threads:[~2025-02-11 12:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 11:57 [PATCH] builtin/refs: add '--skip-reflog' flag to bypass reflog migration Karthik Nayak
2025-02-07 15:23 ` Patrick Steinhardt
2025-02-11  6:18   ` Karthik Nayak
2025-02-07 17:45 ` Justin Tobler
2025-02-11  6:09   ` Karthik Nayak
2025-02-11 11:42 ` [PATCH v2] " Karthik Nayak
2025-02-11 12:21   ` Patrick Steinhardt [this message]
2025-02-11 17:48   ` Junio C Hamano
2025-02-12 17:43     ` Karthik Nayak
2025-02-13  9:25     ` Karthik Nayak
2025-02-12 18:38   ` [PATCH v3] " Karthik Nayak
2025-02-12 22:25     ` Junio C Hamano
2025-02-13  9:22       ` Karthik Nayak
2025-02-13 18:06         ` Junio C Hamano
2025-02-14  8:50           ` Karthik Nayak
2025-02-19 10:06     ` Toon Claes
2025-02-19 17:04       ` Junio C Hamano
2025-02-19 20:28         ` Karthik Nayak
2025-02-19 21:37           ` Junio C Hamano
2025-02-20 10:00             ` Karthik Nayak
2025-02-20  9:56 ` [PATCH v4] builtin/refs: add '--no-reflog' flag to drop reflogs Karthik Nayak
2025-02-20 15:14   ` Junio C Hamano
2025-02-21  8:44     ` Karthik Nayak
2025-02-21 10:04 ` [PATCH v5] " Karthik Nayak
2025-02-21 17:54   ` Junio C Hamano
2025-02-23 20:30     ` Karthik Nayak

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=Z6tA4zC4WhdAVbPD@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@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.