Re: [PATCH 0/3] Close commit-graph before calling 'gc'
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 20, 2019, 09:40 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1905201139120.46@tvgsbejvaqbjf.bet>
- In-Reply-To
- <pull.208.git.gitgitgadget@gmail.com>
Hi Stolee,
On Fri, 17 May 2019, Derrick Stolee via GitGitGadget wrote:
Show 12 quoted lines
> In Windows, the way we rename a lock file to replace the underlying file > does not work when a process holds a read handle. For this reason, we call > close_all_packs() everywhere before starting a git gc --auto subprocess. We > also call close_commit_graph() before renaming the commit-graph lock file. > But we don't close the commit-graph handles before running gc, which can > cause an issue when gc.writeCommitGraph is enabled. > > This series adds close_commit_graph() to close_all_packs() and then renames > close_all_packs() to close_object_store(). This name is more descriptive of > its larger purpose. > > This is based on ds/commit-graph-write-refactor to avoid conflicts.
Thank you so much for jumping on my (off-list, in-team) bug report!
FWIW I integrated this series into Git for Windows v2.22.0-rc1 already.
Thanks, Dscho