git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Paul Smith <paul@mad-scientist.net>, git@vger.kernel.org
Subject: Re: Fetching everything in another bare repo
Date: Fri, 10 Mar 2023 04:04:19 -0500	[thread overview]
Message-ID: <ZArykwkX827/Qpi3@coredump.intra.peff.net> (raw)
In-Reply-To: <20230309175718.j5c2dbx3asphiqhu@meerkat.local>

On Thu, Mar 09, 2023 at 12:57:18PM -0500, Konstantin Ryabitsev wrote:

> > I will also say that while I implemented this extension a while back, it
> > never actually saw production use for my intended case. So I think it's
> > pretty good (and certainly safer than nothing), but it's not thoroughly
> > tested in the wild.
> 
> We use it in grokmirror for objstore repositories [1] (the super-parents of
> all forks), as a precautionary measure against a sysadmin running any kind of
> manual operation that may result in loose objects being deleted. I do believe
> it works well for that purpose.

Ah, cool, thanks for letting us know. That's pretty much the same case I
wrote it for (GitHub's shared-object-store fork repositories), but
deployment got hung up on compatibility issues (since we used libgit2,
as well). And then I never got around to it, and nobody seems to have
cared too much. It's a nice safety to have, but I don't recall a single
instance of an unintended naive gc ever destroying things. :)

-Peff

  reply	other threads:[~2023-03-10  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 22:39 Fetching everything in another bare repo Paul Smith
2023-03-09  6:41 ` Jeff King
2023-03-09 13:55   ` Paul Smith
2023-03-09 15:35     ` Jeff King
2023-03-09 17:57       ` Konstantin Ryabitsev
2023-03-10  9:04         ` Jeff King [this message]
2023-03-09 18:15       ` Paul Smith

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=ZArykwkX827/Qpi3@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=paul@mad-scientist.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 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).