aboutsummaryrefslogtreecommitdiff
path: root/graph.c
diff options
context:
space:
mode:
authorCornelius Weig <cornelius.weig@tngtech.com>2017-01-27 11:09:47 +0100
committerJunio C Hamano <gitster@pobox.com>2017-01-31 10:01:24 -0800
commit341fb28621201c5e6c9d3fee5baf7c532fa8a618 (patch)
tree1968a421d74a50dcc53304dd0196af5cf76b8d14 /graph.c
parentd0c93194ecde2886d4e90d7006c998ea9592d0a0 (diff)
downloadgit-341fb28621201c5e6c9d3fee5baf7c532fa8a618.tar.gz
git-341fb28621201c5e6c9d3fee5baf7c532fa8a618.tar.xz
refs: add option core.logAllRefUpdates = always
When core.logallrefupdates is true, we only create a new reflog for refs that are under certain well-known hierarchies. The reason is that we know that some hierarchies (like refs/tags) are not meant to change, and that unknown hierarchies might not want reflogs at all (e.g., a hypothetical refs/foo might be meant to change often and drop old history immediately). However, sometimes it is useful to override this decision and simply log for all refs, because the safety and audit trail is more important than the performance implications of keeping the log around. This patch introduces a new "always" mode for the core.logallrefupdates option which will log updates to everything under refs/, regardless where in the hierarchy it is (we still will not log things like ORIG_HEAD and FETCH_HEAD, which are known to be transient). Based-on-patch-by: Jeff King <peff@peff.net> Signed-off-by: Cornelius Weig <cornelius.weig@tngtech.com> Reviewed-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'graph.c')
0 files changed, 0 insertions, 0 deletions