All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marco Luzzara via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Marco Luzzara <marco.luzzara@hotmail.it>,
	Marco Luzzara <marco.luzzara@hotmail.it>
Subject: [PATCH] docs: clarified that --lost-found implies --no-reflogs
Date: Mon, 01 Mar 2021 15:02:00 +0000	[thread overview]
Message-ID: <pull.970.git.git.1614610921331.gitgitgadget@gmail.com> (raw)

From: Marco Luzzara <marco.luzzara@hotmail.it>

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>
---
    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: git fsck
    combining --lost-found and --unreachable
    [https://stackoverflow.com/questions/66401232/git-fsck-combining-lost-found-and-unreachable]

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-970%2Fmarco-luzzara%2Fmaster-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-970/marco-luzzara/master-v1
Pull-Request: https://github.com/git/git/pull/970

 Documentation/git-fsck.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt
index bd596619c0d3..9f1db29042f0 100644
--- a/Documentation/git-fsck.txt
+++ b/Documentation/git-fsck.txt
@@ -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

base-commit: 225365fb5195e804274ab569ac3cc4919451dc7f
-- 
gitgitgadget

             reply	other threads:[~2021-03-01 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 15:02 Marco Luzzara via GitGitGadget [this message]
2021-03-01 19:02 ` [PATCH] docs: clarified that --lost-found implies --no-reflogs Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.970.git.git.1614610921331.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marco.luzzara@hotmail.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.