1
0
Fork 0
mirror of https://github.com/git/git.git synced 2024-05-09 14:56:07 +02:00

docs: clarified that --lost-found implies --no-reflogs

git fsck --lost-found does not look for references in the reflog. If not specified, it could create misunderstandings like this one: https://stackoverflow.com/questions/66401232/git-fsck-combining-lost-found-and-unreachable

Signed-off-by: Marco Luzzara <marco.luzzara@hotmail.it>
This commit is contained in:
Marco Luzzara 2021-03-01 11:38:10 +01:00
parent 225365fb51
commit 822b7bbd38

View File

@ -89,7 +89,7 @@ care about this output and want to speed it up further.
Write dangling objects into .git/lost-found/commit/ or
.git/lost-found/other/, depending on type. If the object is
a blob, the contents are written into the file, rather than
its object name.
its object name. This option implies `--no-reflogs`.
--name-objects::
When displaying names of reachable objects, in addition to the