mirror of
https://github.com/git/git.git
synced 2025-01-19 22:13:32 +08:00
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>
This commit is contained in:
parent
df25a19d72
commit
0464d0a134
@ -16,8 +16,7 @@
|
|||||||
* This backend uses the following flags in `ref_update::flags` for
|
* This backend uses the following flags in `ref_update::flags` for
|
||||||
* internal bookkeeping purposes. Their numerical values must not
|
* internal bookkeeping purposes. Their numerical values must not
|
||||||
* conflict with REF_NO_DEREF, REF_FORCE_CREATE_REFLOG, REF_HAVE_NEW,
|
* conflict with REF_NO_DEREF, REF_FORCE_CREATE_REFLOG, REF_HAVE_NEW,
|
||||||
* REF_HAVE_OLD, or REF_IS_PRUNING, which are also stored in
|
* or REF_HAVE_OLD, which are also stored in `ref_update::flags`.
|
||||||
* `ref_update::flags`.
|
|
||||||
*/
|
*/
|
||||||
|
|
||||||
/*
|
/*
|
||||||
|
Loading…
Reference in New Issue
Block a user