On Mon, Oct 19, 2015 at 11:09:19PM +, brian m. carlson wrote:
> On Mon, Oct 19, 2015 at 08:59:15PM +0100, Andreas Amann wrote:
> > Thank you for your answer. However, this reasoning only applies to loose
> > objects and not packfiles.
> >
> > My understanding is that "git prune" will not pru
On Mon, Oct 19, 2015 at 08:59:15PM +0100, Andreas Amann wrote:
> Thank you for your answer. However, this reasoning only applies to loose
> objects and not packfiles.
>
> My understanding is that "git prune" will not prune any pack files
> (except those starting with tmp_). Only "git repack" sho
"brian m. carlson" writes:
> On Sun, Oct 18, 2015 at 10:37:55PM +0100, Andreas Amann wrote:
>> git (2.6.1) sometimes updates the modification time of a packfile, even if it
>> has not changed at all.
>>
>> On my system this triggers quite expensive an d unnecessary backup
>> operations, which I w
On Sun, Oct 18, 2015 at 10:37:55PM +0100, Andreas Amann wrote:
> git (2.6.1) sometimes updates the modification time of a packfile, even if it
> has not changed at all.
>
> On my system this triggers quite expensive an d unnecessary backup
> operations, which I would prefer to avoid. Is there a s
git (2.6.1) sometimes updates the modification time of a packfile, even if it
has not changed at all.
On my system this triggers quite expensive an d unnecessary backup
operations, which I would prefer to avoid. Is there a simple way to
keep the mtime of packfiles fixed, once they are created?
A
5 matches
Mail list logo
