On 2017-03-07 13:33, Junio C Hamano wrote:
James Melvin writes:
...
I am not sure if I understand your design. Your model looks to me
like there are two modes of operation. #1 uses "--preserve-old" and
sends old ones to purgatory instead of removing them and #2
On Thursday, March 09, 2017 10:50:21 AM
jmel...@codeaurora.org wrote:
> On 2017-03-07 13:33, Junio C Hamano wrote:
> > James Melvin writes:
> >> These options are designed to prevent stale file handle
> >> exceptions during git operations which can happen on
> >> users of
On 2017-03-07 13:33, Junio C Hamano wrote:
James Melvin writes:
These options are designed to prevent stale file handle exceptions
during git operations which can happen on users of NFS repos when
repacking is done on them. The strategy is to preserve old pack files
James Melvin writes:
> These options are designed to prevent stale file handle exceptions
> during git operations which can happen on users of NFS repos when
> repacking is done on them. The strategy is to preserve old pack files
> around until the next repack with the
The new --preserve-oldpacks option moves old pack files into the
preserved subdirectory instead of deleting them after repacking.
The new --prune-preserved option prunes old pack files from the
preserved subdirectory after repacking, but before potentially
moving the latest old packfiles to this
5 matches
Mail list logo