Re: worktrees vs. alternates
- From
- Martin Fick <mfick@codeaurora.org>
- Date
- May 16, 2018, 19:40 UTC
- Message-ID
- <42435260.5sd4EuToWN@mfick-lnx>
- In-Reply-To
- <20180516193744.GA4036@sigill.intra.peff.net>
On Wednesday, May 16, 2018 12:37:45 PM Jeff King wrote:
> On Wed, May 16, 2018 at 03:29:42PM -0400, Konstantin
Ryabitsev wrote:
Show 10 quoted lines
> Yes, that's pretty close to what we do at GitHub. Before > doing any repacking in the mother repo, we actually do > the equivalent of: > > git fetch --prune ../$id.git +refs/*:refs/remotes/$id/* > git repack -Adl > > from each child to pick up any new objects to de-duplicate > (our "mother" repos are not real repos at all, but just > big shared-object stores).
...
> In theory the fetch means that it's safe to actually prune > in the mother repo, but in practice there are still > races. They don't come up often, but if you have enough > repositories, they do eventually. :)
Peff,
I would be very curious to hear what you think of this approach to mitigating the effect of those races?
https://git.eclipse.org/r/c/122288/2
-Martin
-- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation