From: Paul Smith <paul@mad-scientist.net>
To: git@vger.kernel.org
Subject: Re: Fetching everything in another bare repo
Date: Thu, 09 Mar 2023 13:15:33 -0500 [thread overview]
Message-ID: <42ea54b4b4d74d6760faca8325a657ee71f342d7.camel@mad-scientist.net> (raw)
In-Reply-To: <ZAn80gnIFLOF4Gco@coredump.intra.peff.net>
On Thu, 2023-03-09 at 10:35 -0500, Jeff King wrote:
> > Basically, these bare clones have "gc.pruneExpire=never" set, and
> > have never had any GC operations run so all commits are still
> > present (when you say "unreachable" I assume you mean, not
> > reachable through any reference).
>
> Right, that's what I mean by unreachable. And no, you didn't use any
> terminology wrong. I was just not sure if you realized that running
> "fetch" would not get the unreachable objects. :)
I definitely did not realize that, so good looking out :)
Of course in retrospect it makes perfect sense: why would you fetch
unreachable objects (normally)?
> > One question: is the objects/info/packs file anything to be
> > concerned about or will git repack (or something) take care of
> > handling it?
>
> You can ignore it.
OK thx.
> Yeah, if you have a separate database of branch tips, etc, then the
> refs aren't necessary. As long as you are careful not to run "gc" or
> repack without "-k".
It's actually a code review facility so it doesn't even care about
branches, it's basically just storing before/after SHAs of changes to
be reviewed. But the historical code reviews can sometimes be gold,
even if they're some years old, so I'd prefer to keep them available.
> You may want to try the "preciousObjects" repository extension, which
> was designed to prevent accidents for a case like this.
Oh interesting, I'll take a look.
Cheers!
prev parent reply other threads:[~2023-03-09 18:16 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
2023-03-09 18:15 ` Paul Smith [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42ea54b4b4d74d6760faca8325a657ee71f342d7.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).