summaryrefslogtreecommitdiff
path: root/shallow.c
diff options
context:
space:
mode:
authorMichael Haggerty <mhagger@alum.mit.edu>2014-12-12 08:56:47 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-12-12 19:43:47 (GMT)
commit60cc3c4072259609aefbdbc762d1f72bcbd97783 (patch)
treefb574895a06797d32f327001edb47bf19c94442c /shallow.c
parentf3b661f766c1525265d065fdd0529985979c80c6 (diff)
downloadgit-60cc3c4072259609aefbdbc762d1f72bcbd97783.zip
git-60cc3c4072259609aefbdbc762d1f72bcbd97783.tar.gz
git-60cc3c4072259609aefbdbc762d1f72bcbd97783.tar.bz2
Extract function should_expire_reflog_ent()
Extract from expire_reflog_ent() a function that is solely responsible for deciding whether a reflog entry should be expired. By separating this "business logic" from the mechanics of actually expiring entries, we are working towards the goal of encapsulating reflog expiry within the refs API, with policy decided by a callback function passed to it by its caller. Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'shallow.c')
0 files changed, 0 insertions, 0 deletions