From: Jeff King <peff@peff.net>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"ZheNing Hu" <adlternative@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Christian Couder" <christian.couder@gmail.com>,
johncai86@gmail.com, "Taylor Blau" <me@ttaylorr.com>
Subject: Re: Question: How to execute git-gc correctly on the git server
Date: Thu, 8 Dec 2022 02:01:05 -0500 [thread overview]
Message-ID: <Y5GLsZgmrxbBtLqo@coredump.intra.peff.net> (raw)
In-Reply-To: <20221208011631.GH28810@kitsune.suse.cz>
On Thu, Dec 08, 2022 at 02:16:31AM +0100, Michal Suchánek wrote:
> > A "git gc" on a "live" repo is always racy in theory, but the odds that
> > you'll run into data corrupting trouble tends to approach zero as you
> > increase the gc.pruneExpire setting, with the default 2 weeks being more
> > than enough for even the most paranoid user.
>
> And that two weeks expiration applies to what, exactly?
>
> For commits there is author date and commit date but many other objecs
> won't have these I suppose. And the date when the object is pushed into
> the repository is unrelated to these two, anyway.
In this case it's the mtime on the object file (or the pack containing
it). But yes, it is far from a complete race-free solution.
-Peff
next prev parent reply other threads:[~2022-12-08 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 15:58 Question: How to execute git-gc correctly on the git server ZheNing Hu
2022-12-07 23:57 ` Ævar Arnfjörð Bjarmason
2022-12-08 1:16 ` Michal Suchánek
2022-12-08 7:01 ` Jeff King [this message]
2022-12-09 0:49 ` Michal Suchánek
2022-12-09 1:37 ` Jeff King
2022-12-09 7:26 ` ZheNing Hu
2022-12-09 13:48 ` Ævar Arnfjörð Bjarmason
2022-12-11 16:01 ` ZheNing Hu
2022-12-11 16:27 ` Michal Suchánek
2022-12-09 7:15 ` ZheNing Hu
2022-12-08 6:59 ` Jeff King
2022-12-08 12:35 ` Ævar Arnfjörð Bjarmason
2022-12-14 20:11 ` Taylor Blau
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=Y5GLsZgmrxbBtLqo@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=adlternative@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johncai86@gmail.com \
--cc=me@ttaylorr.com \
--cc=msuchanek@suse.de \
/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).