| commit | a5e10f8bc1db418fc806abb7574bb1e468948d19 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Mon, 9 Sep 2013 21:27:11 +0000 (9 14:27 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 9 Sep 2013 21:27:11 +0000 (9 14:27 -0700) | ||
| tree | 7b16be6b855c74eaa6534fa758f41d784ba2b846 | treesnapshot (tar.gz zip) |
| parent | bd5424f0d6257b55f7269ee5f009c5ce5eb71c6e | commitdiff |
| parent | 737c5a9cde708d6995c765b7c2e95033edd0a896 | commitdiff |
Merge branch 'ms/fetch-prune-configuration'
Allow fetch.prune and remote.*.prune configuration variables to be set,
and "git fetch" to behave as if "--prune" is given.
"git fetch" that honors remote.*.prune is fine, but I wonder if we
should somehow make "git push" aware of it as well. Perhaps
remote.*.prune should not be just a boolean, but a 4-way "none",
"push", "fetch", "both"?
* ms/fetch-prune-configuration:
fetch: make --prune configurable
Allow fetch.prune and remote.*.prune configuration variables to be set,
and "git fetch" to behave as if "--prune" is given.
"git fetch" that honors remote.*.prune is fine, but I wonder if we
should somehow make "git push" aware of it as well. Perhaps
remote.*.prune should not be just a boolean, but a 4-way "none",
"push", "fetch", "both"?
* ms/fetch-prune-configuration:
fetch: make --prune configurable
| Documentation/config.txt | diff1 | diff2 | blobhistory |
| builtin/fetch.c | diff1 | diff2 | blobhistory |
| remote.c | diff1 | diff2 | blobhistory |
| t/t5510-fetch.sh | diff1 | diff2 | blobhistory |