undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: git gc packs refs by default now

Browse Source 
In commit 56752391 (Make "git gc" pack all refs by default,
2007-05-24), 'git gc' was changed to run pack-refs by default

Versions before v1.5.1.2 cannot clone repos with packed refs over
http, and versions before v1.4.4 cannot handled packed refs at
all, but more recent git should have no problems.  Try to make
this more clear in the git-config manual.

The analagous passage in git-gc.txt was updated already with
commit fe2128a (Change git-gc documentation to reflect
gc.packrefs implementation., 2008-01-09).

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Jonathan Nieder 2010-01-09 20:59:41 -06:00 committed by Junio C Hamano
parent dc89689e86
commit efc266e8ae
1 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Documentation/config.txt
View File

@ -875,15 +875,12 @@ gc.autopacklimit::
default value is 50. Setting this to 0 disables it. default value is 50. Setting this to 0 disables it.
gc.packrefs:: gc.packrefs::
'git-gc' does not run `git pack-refs` in a bare repository by Running `git pack-refs` in a repository renders it
default so that older dumb-transport clients can still fetch unclonable by Git versions prior to 1.5.1.2 over dumb
from the repository. Setting this to `true` lets 'git-gc' transports such as HTTP. This variable determines whether
to run `git pack-refs`. Setting this to `false` tells 'git gc' runs `git pack-refs`. This can be set to "nobare"
'git-gc' never to run `git pack-refs`. The default setting is to enable it within all non-bare repos or it can be set to a
`notbare`. Enable it only when you know you do not have to boolean value. The default is `true`.
support such clients. The default setting will change to `true`
at some stage, and setting this to `false` will continue to
prevent `git pack-refs` from being run from 'git-gc'.
gc.pruneexpire:: gc.pruneexpire::
When 'git-gc' is run, it will call 'prune --expire 2.weeks.ago'. When 'git-gc' is run, it will call 'prune --expire 2.weeks.ago'.