All of lore.kernel.org
 help / color / mirror / Atom feed
From: "ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, me@ttaylorr.com, ZheNing Hu <adlternative@gmail.com>
Subject: [PATCH v2 0/2] gc: add --expire-to option
Date: Tue, 31 Dec 2024 02:18:31 +0000	[thread overview]
Message-ID: <pull.1843.v2.git.1735611513.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1843.git.1735041177817.gitgitgadget@gmail.com>

I want to perform a "safe" garbage collection for the Git repository on the
server, which avoids data corruption issues caused by concurrent pushes
during git GC. To achieve this, I currently need to use git repack --cruft
--expire-to=<dir> and git prune in combination. However, it would be simpler
if we could directly use --expire-to=<dir> with the git-gc command.

ZheNing Hu (2):
  gc: add `--expire-to` option
  fix(gc): make --prune=now compatible with --expire-to

 Documentation/git-gc.txt | 6 ++++++
 builtin/gc.c             | 9 +++++++--
 t/t6500-gc.sh            | 6 ++++++
 3 files changed, 19 insertions(+), 2 deletions(-)


base-commit: 92999a42db1c5f43f330e4f2bca4026b5b81576f
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1843%2Fadlternative%2Fzh%2Fgc-expire-to-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1843/adlternative/zh/gc-expire-to-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/1843

Range-diff vs v1:

 1:  14e94bf04e5 = 1:  14e94bf04e5 gc: add `--expire-to` option
 -:  ----------- > 2:  579757957d2 fix(gc): make --prune=now compatible with --expire-to

-- 
gitgitgadget

  reply	other threads:[~2024-12-31  2:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24 11:52 [PATCH] gc: add `--expire-to` option ZheNing Hu via GitGitGadget
2024-12-31  2:18 ` ZheNing Hu via GitGitGadget [this message]
2024-12-31  2:18   ` [PATCH v2 1/2] " ZheNing Hu via GitGitGadget
2025-01-03  4:57     ` ZheNing Hu
2025-01-13  7:12     ` ZheNing Hu
2024-12-31  2:18   ` [PATCH v2 2/2] fix(gc): make --prune=now compatible with --expire-to ZheNing Hu via GitGitGadget
2025-01-13  9:17     ` Jeff King
2025-01-15  7:56       ` ZheNing Hu
2025-01-16  2:35   ` [PATCH v3] gc: add `--expire-to` option ZheNing Hu via GitGitGadget
2025-01-16 18:23     ` Junio C Hamano
2025-01-23  3:42       ` ZheNing Hu
2025-01-24  7:49     ` [PATCH v4] " ZheNing Hu via GitGitGadget
2025-02-04 18:15       ` Junio C Hamano

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=pull.1843.v2.git.1735611513.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=adlternative@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.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.