| commit | 04a00a7021e9d14c53e943f03c0c19e102c4dece | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Tue, 28 Apr 2015 10:54:16 +0000 (28 03:54 -0700) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Tue, 28 Apr 2015 10:54:16 +0000 (28 03:54 -0700) | ||
| tree | 67c6295534a8f9dfa2fa0292909d0f78df8c85cf | treesnapshot (tar.gz zip) |
| parent | 878a741422bcfa6c472cba5e4df5506d6af8a2d7 | commitdiff |
Project.pm: set core.logallrefupdates to false
In a bare repository core.logallrefupdates normally defaults to
false. However, some Git commands will actually behave as though
it's set to true if it's left unset even in a bare repository.
While it's unlikely Girocco would be running any of these commands,
should an administrator run them in a repository, a repository could
end up with ref logs that would interfere with efficient gc.
Therefore always set core.logallrefupdates explicitly to false when
we initially create the repository.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
In a bare repository core.logallrefupdates normally defaults to
false. However, some Git commands will actually behave as though
it's set to true if it's left unset even in a bare repository.
While it's unlikely Girocco would be running any of these commands,
should an administrator run them in a repository, a repository could
end up with ref logs that would interfere with efficient gc.
Therefore always set core.logallrefupdates explicitly to false when
we initially create the repository.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
| Girocco/Project.pm | diffblobblamehistory |