From: Taylor Blau <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, firstname.lastname@example.org Subject: [PATCH 0/3] repack: don't move existing packs out of the way Date: Mon, 16 Nov 2020 13:41:04 -0500 [thread overview] Message-ID: <email@example.com> (raw) Hi, Here are a few patches that GitHub has been running to get rid of the rename-to-old behavior that 'git repack' has when its invocation of 'pack-objects' produced a pack that already exists. This was developed in the context of a circular dependency involving writing a multi-pack index during 'git repack' (we have some patches that do so by adding a '--write-midx' in the repack builtin), but it should be generally useful. The idea (which is explained in detail in the final patch) is that prior to 1190a1acf8 (pack-objects: name pack files after trailer hash, 2013-12-05), 'git repack' had to move existing packs out of the way for safety, but after 1190a1acf8 no longer needs to do so. This makes 'git repack' a little simpler since it no longer has to deal with any failures encountered during this rename-to-old behavior. It also paves the way for sending the MIDX-during-repack patches. Thanks, Taylor Jeff King (1): repack: make "exts" array available outside cmd_repack() Taylor Blau (2): builtin/repack.c: keep track of what pack-objects wrote builtin/repack.c: don't move existing packs out of the way builtin/repack.c | 153 +++++++++++++++++------------------------------ 1 file changed, 54 insertions(+), 99 deletions(-) -- 188.8.131.522.gabc4d358d8
next reply other threads:[~2020-11-16 18:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-16 18:41 Taylor Blau [this message] 2020-11-16 18:41 ` [PATCH 1/3] repack: make "exts" array available outside cmd_repack() Taylor Blau 2020-11-16 18:41 ` [PATCH 2/3] builtin/repack.c: keep track of what pack-objects wrote Taylor Blau 2020-11-16 18:41 ` [PATCH 3/3] builtin/repack.c: don't move existing packs out of the way Taylor Blau 2020-11-16 23:29 ` Junio C Hamano 2020-11-17 0:02 ` Jeff King 2020-11-17 0:26 ` Taylor Blau 2020-11-17 0:25 ` Taylor Blau 2020-11-17 0:46 ` Junio C Hamano 2020-11-17 20:15 ` Taylor Blau 2020-11-17 21:28 ` 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 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/3] repack: don'\''t move existing packs out of the way' \ /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
Code repositories for project(s) associated with this 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).