From: "Manish Goregaokar via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] doc: Correct man page for the SHAs reported by 'submodule status'
Date: Fri, 22 Nov 2019 23:11:24 +0000 [thread overview]
Message-ID: <pull.470.git.1574464285.gitgitgadget@gmail.com> (raw)
The documentation is currently incorrect, it talks about the checked out
SHAs when git submodule status actually reports the superproject's tracked
SHAs.
It's possible (but unlikely IMO) that we should change the behavior of the
tool to match the documentation. A flag for this behavior may be useful.
Manish Goregaokar (1):
Documentation: Correct man page for the SHAs reported by 'submodule
status'
Documentation/git-submodule.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: 5fa0f5238b0cd46cfe7f6fa76c3f526ea98148d9
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-470%2FManishearth%2Fsubmodule-sha-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-470/Manishearth/submodule-sha-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/470
--
gitgitgadget
next reply other threads:[~2019-11-22 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 23:11 Manish Goregaokar via GitGitGadget [this message]
2019-11-22 23:11 ` [PATCH 1/1] Documentation: Correct man page for the SHAs reported by 'submodule status' Manish Goregaokar via GitGitGadget
2019-11-23 1:21 ` Junio C Hamano
2019-11-23 5:46 ` Manish Goregaokar
2019-11-23 5:54 ` [PATCH v2 0/1] doc: Document 'git submodule status --cached' Manish Goregaokar via GitGitGadget
2019-11-23 5:54 ` [PATCH v2 1/1] " Manish Goregaokar via GitGitGadget
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.470.git.1574464285.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).