Web lists-archives.com

Re: [PATCH v4 20/21] gc: automatically write commit-graph files




On Mon, Jun 04 2018, Derrick Stolee wrote:

> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 11f027194e..d2eb3c8e9b 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -900,7 +900,8 @@ the `GIT_NOTES_REF` environment variable.  See linkgit:git-notes[1].
>
>  core.commitGraph::
>  	Enable git commit graph feature. Allows reading from the
> -	commit-graph file.
> +	commit-graph file. See `gc.commitGraph` for automatically
> +	maintaining the file.
>
>  core.sparseCheckout::
>  	Enable "sparse checkout" feature. See section "Sparse checkout" in
> @@ -1553,6 +1554,13 @@ gc.autoDetach::
>  	Make `git gc --auto` return immediately and run in background
>  	if the system supports it. Default is true.
>
> +gc.commitGraph::
> +	If true, then gc will rewrite the commit-graph file when
> +	linkgit:git-gc[1] is run. When using linkgit:git-gc[1]
> +	'--auto' the commit-graph will be updated if housekeeping is
> +	required. Default is false. See linkgit:git-commit-graph[1]
> +	for details.
> +
>  gc.logExpiry::
>  	If the file gc.log exists, then `git gc --auto` won't run
>  	unless that file is more than 'gc.logExpiry' old.  Default is

Re my last E-Mail in
https://public-inbox.org/git/87k1rcyxxj.fsf@xxxxxxxxxxxxxxxxxxx/
88258f58-c28f-0f74-a378-003704c41117@xxxxxxxxx and your reply in
https://public-inbox.org/git/88258f58-c28f-0f74-a378-003704c41117@xxxxxxxxx/
it seems what you've submitted here is the old version. E.g. this hunk
fails to apply to master because of the conflict with
gc.bigPackThreshold, which was merged in 30b015bffe ("Merge branch
'nd/repack-keep-pack'", 2018-05-23) .