diff options
author | Han-Wen Nienhuys <hanwen@google.com> | 2021-12-07 14:38:16 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2021-12-07 22:15:19 +0100 |
commit | 0464d0a134df97c3f9475c58e536c3b685a3ff7d (patch) | |
tree | 43acc942818d2ab364b3b622012652d79bc6f116 /refs | |
parent | test-ref-store: plug memory leak in cmd_delete_refs (diff) | |
download | git-0464d0a134df97c3f9475c58e536c3b685a3ff7d.tar.xz git-0464d0a134df97c3f9475c58e536c3b685a3ff7d.zip |
refs: update comment.
REF_IS_PRUNING is right below this comment, so it clearly does not belong in
this comment. This was apparently introduced in commit 5ac95fee (Nov 5, 2017
"refs: tidy up and adjust visibility of the `ref_update` flags").
Signed-off-by: Han-Wen Nienhuys <hanwen@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'refs')
-rw-r--r-- | refs/files-backend.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/refs/files-backend.c b/refs/files-backend.c index 4b14f30d48..37329b98cc 100644 --- a/refs/files-backend.c +++ b/refs/files-backend.c @@ -16,8 +16,7 @@ * This backend uses the following flags in `ref_update::flags` for * internal bookkeeping purposes. Their numerical values must not * conflict with REF_NO_DEREF, REF_FORCE_CREATE_REFLOG, REF_HAVE_NEW, - * REF_HAVE_OLD, or REF_IS_PRUNING, which are also stored in - * `ref_update::flags`. + * or REF_HAVE_OLD, which are also stored in `ref_update::flags`. */ /* |