From: Stefan Beller <sbeller@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Jens.Lehmann@web.de, hvoigt@hvoigt.net,
Stefan Beller <sbeller@google.com>
Subject: [PATCH] documentation: clarify submodule.<name>.[url, path] variables
Date: Thu, 6 Oct 2016 16:51:49 -0700 [thread overview]
Message-ID: <20161006235149.10232-1-sbeller@google.com> (raw)
Signed-off-by: Stefan Beller <sbeller@google.com>
---
This was raised in the discussion of
https://public-inbox.org/git/20161006193725.31553-1-sbeller@google.com/raw
However this can go as a separate patch instead of adding it to the series.
Thanks,
Stefan
Documentation/config.txt | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index e78293b..1f68d05 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -2812,11 +2812,18 @@ stash.showStat::
See description of 'show' command in linkgit:git-stash[1].
submodule.<name>.path::
+ The path within this project for a submodule. This variable is
+ kept in the .gitmodules file. See linkgit:git-submodule[1] and
+ linkgit:gitmodules[5] for details.
+
submodule.<name>.url::
- The path within this project and URL for a submodule. These
- variables are initially populated by 'git submodule init'. See
- linkgit:git-submodule[1] and linkgit:gitmodules[5] for
- details.
+ The URL for a submodule. This variable is copied from the .gitmodules
+ file to the git config via 'git submodule init'. The user can change
+ the configured URL before obtaining the submodule via 'git submodule
+ update'. After obtaining the submodule, this variable is kept in the
+ config as a boolean flag to indicate whether the submodule is of
+ interest to git commands. See linkgit:git-submodule[1] and
+ linkgit:gitmodules[5] for details.
submodule.<name>.update::
The default update procedure for a submodule. This variable
--
2.10.1.353.g1629400
next reply other threads:[~2016-10-06 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 23:51 Stefan Beller [this message]
2016-10-10 18:09 ` [PATCH] documentation: clarify submodule.<name>.[url, path] variables Junio C Hamano
2016-10-10 18:35 ` Stefan Beller
2016-10-10 19:10 ` Junio C Hamano
2016-10-10 19:36 ` [PATCHv2] documentation: improve submodule.<name>.{url, path} description Stefan Beller
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=20161006235149.10232-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
/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.