[PATCH v4 4/8] refs: update comment.
- From
Han-Wen Nienhuys via GitGitGadget <gitgitgadget@gmail.com>
- Date
- Dec 7, 2021, 13:38 UTC
- Message-ID
- <67d22211ac4b1b62b2c3f76893765255a59ade8a.1638884300.git.gitgitgadget@gmail.com>
- In-Reply-To
- <pull.1147.v4.git.git.1638884300.gitgitgadget@gmail.com>
From: Han-Wen Nienhuys <hanwen@google.com>
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> --- refs/files-backend.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/refs/files-backend.c b/refs/files-backend.c index 4b14f30d48f..37329b98cca 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`. */ /*
-- gitgitgadget