From: Marc Branchaud <marcnarc@xiplink.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v2 2/7] fetch/pull: Add the 'on-demand' value to the --recurse-submodules option
Date: Wed, 02 Mar 2011 11:00:29 -0500 [thread overview]
Message-ID: <4D6E699D.3040000@xiplink.com> (raw)
In-Reply-To: <4D6D7ADA.6090302@web.de>
On 11-03-01 06:01 PM, Jens Lehmann wrote:
> Until now the --recurse-submodules option could only be used to either
> fetch all populated submodules recursively or to disable recursion
> completely. As fetch and pull now by default just fetch those submodules
> for which new commits have been fetched in the superproject, a command
> line option to enforce that behavior is needed to be able to override
> configuration settings.
Strictly speaking, this patch should add the 'on-demand' value to the first
patch's --submodule-default option. Perhaps I'm being a bit too uptight
though...
> Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
> ---
> Documentation/fetch-options.txt | 16 +++++++--
> Documentation/git-pull.txt | 2 +-
> builtin/fetch.c | 22 ++++++++++--
> git-pull.sh | 3 ++
> submodule.c | 8 +++-
> submodule.h | 2 +-
> t/t5526-fetch-submodules.sh | 71 +++++++++++++++++++++++++++++++++++++++
> 7 files changed, 114 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
> index ae22f75..f28c0b1 100644
> --- a/Documentation/fetch-options.txt
> +++ b/Documentation/fetch-options.txt
> @@ -65,9 +65,19 @@ ifndef::git-pull[]
> specified with the remote.<name>.tagopt setting. See
> linkgit:git-config[1].
>
> ---[no-]recurse-submodules::
> - This option controls if new commits of all populated submodules should
> - be fetched too (see linkgit:git-config[1] and linkgit:gitmodules[5]).
> +--recurse-submodules[=yes|on-demand|no]::
> + This option controls if and under what conditions new commits of all
Nit: Remove "all" from the above line.
> + populated submodules should be fetched too. It can be used as a
> + boolean option to completely disable recursion when set to 'no' or to
> + unconditionally recurse into all populated submodules when set to
> + 'yes', which is the default when this option is used without any
> + value. If 'on-demand' is used, it will only recurse into those
> + submodules where new commits have been fetched in the superproject
> + (also see linkgit:git-config[1] and linkgit:gitmodules[5]).
Nit: Replace that last sentence with
Use 'on-demand' to only recurse into a submodule when the
superproject retrieves a commit that updates the submodule's
reference.
Also, this has to change again with patch 5 (Don't recurse into a submodule
when commits are already present).
M.
next prev parent reply other threads:[~2011-03-02 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 22:59 [PATCH v2 0/7] Teach fetch/pull the on-demand mode and make it the default Jens Lehmann
2011-03-01 23:01 ` [PATCH v2 1/7] fetch/pull: recurse into submodules when necessary Jens Lehmann
2011-03-02 15:42 ` Marc Branchaud
2011-03-01 23:01 ` [PATCH v2 2/7] fetch/pull: Add the 'on-demand' value to the --recurse-submodules option Jens Lehmann
2011-03-02 16:00 ` Marc Branchaud [this message]
2011-03-02 16:02 ` Marc Branchaud
2011-03-01 23:02 ` [PATCH v3 3/7] config: teach the fetch.recurseSubmodules option the 'on-demand' value Jens Lehmann
2011-03-02 16:02 ` Marc Branchaud
2011-03-01 23:03 ` [PATCH v2 4/7] Submodules: Add 'on-demand' value for the 'fetchRecurseSubmodule' option Jens Lehmann
2011-03-01 23:03 ` [PATCH v2 5/7] fetch/pull: Don't recurse into a submodule when commits are already present Jens Lehmann
2011-03-02 16:08 ` Marc Branchaud
2011-03-01 23:04 ` [PATCH v2 6/7] submodule update: Don't fetch when the submodule commit is " Jens Lehmann
2011-03-01 23:04 ` [PATCH v2 7/7] fetch/pull: Describe --recurse-submodule restrictions in the BUGS section Jens Lehmann
2011-03-02 20:53 ` Jens Lehmann
2011-03-02 16:09 ` [PATCH v2 0/7] Teach fetch/pull the on-demand mode and make it the default Marc Branchaud
2011-03-02 23:35 ` Jens Lehmann
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6E699D.3040000@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).