From: "elonderin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: thomas menzel <github@tomsit.de>,
Junio C Hamano <gitster@pobox.com>,
elonderin <8225602+elonderin@users.noreply.github.com>
Subject: [PATCH 1/1] doc: submodule: fix typo for command absorbgitdirs
Date: Mon, 06 Jan 2020 14:50:13 +0000 [thread overview]
Message-ID: <b032358ca97df3bd5605ff356196f82a1f16a320.1578322213.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.688.git.git.1578322213.gitgitgadget@gmail.com>
From: elonderin <8225602+elonderin@users.noreply.github.com>
The sentence wants to talk about the superproject's possesive, not plural form.
Signed-off-by: thomas menzel dev@tomsit.de
---
Documentation/git-submodule.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
index 22425cbc76..5232407f68 100644
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -248,7 +248,7 @@ registered submodules, and sync any nested submodules within.
absorbgitdirs::
If a git directory of a submodule is inside the submodule,
- move the git directory of the submodule into its superprojects
+ move the git directory of the submodule into its superproject's
`$GIT_DIR/modules` path and then connect the git directory and
its working directory by setting the `core.worktree` and adding
a .git file pointing to the git directory embedded in the
--
gitgitgadget
next prev parent reply other threads:[~2020-01-06 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 14:50 [PATCH 0/1] doc: fixed a typo in git-submodule.txt thomas menzel via GitGitGadget
2020-01-06 14:50 ` elonderin via GitGitGadget [this message]
2020-01-06 17:13 ` [PATCH 1/1] doc: submodule: fix typo for command absorbgitdirs Junio C Hamano
2020-01-06 17:18 ` Junio C Hamano
2020-01-06 22:52 ` Johannes Schindelin
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=b032358ca97df3bd5605ff356196f82a1f16a320.1578322213.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=8225602+elonderin@users.noreply.github.com \
--cc=git@vger.kernel.org \
--cc=github@tomsit.de \
--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).