> +information from taking up too much space on disk or in memory. Some
> +git commands may automatically run linkgit:git-gc[1], so you don't
> +have to worry about running it manually. However, compressing large
> +repositories may take some time, so you might want to disable
> +automatic comres
"W. Trevor King" writes:
> I just read through the manual cover to cover, so I have a number of
> other fixes in the pipe (from which I've already submitted the
> receive.denyCurrentBranch patch).
Wonderful.
> ... Should I bundle them all into a
> single series to reduce clutter on the list,..
"W. Trevor King" writes:
> I just read through the manual cover to cover, so I have a number of
> other fixes in the pipe (from which I've already submitted the
> receive.denyCurrentBranch patch).
Wonderful.
> ... Should I bundle them all into a
> single series to reduce clutter on the list,..
On Fri, Feb 08, 2013 at 09:36:53AM -0800, Junio C Hamano wrote:
> I'd rather phrase it like "... may take long, so you would want to
> run it explicitly from time to time to avoid automatic gc kicking in
> when it is not convenient for you".
Works for me.
> Removal of this is a good change, thoug
"W. Trevor King" writes:
> From: "W. Trevor King"
>
> This should have happened back in 2007, when `git gc` learned about
> auto:
>
> commit e9831e83e063844b90cf9e525d0003715dd8b395
> Author: Junio C Hamano
> Date: Mon Sep 17 00:39:52 2007 -0700
>
> git-gc --auto: add documentation.
From: "W. Trevor King"
This should have happened back in 2007, when `git gc` learned about
auto:
commit e9831e83e063844b90cf9e525d0003715dd8b395
Author: Junio C Hamano
Date: Mon Sep 17 00:39:52 2007 -0700
git-gc --auto: add documentation.
Signed-off-by: W. Trevor King
---
I'd als
6 matches
Mail list logo
