From: Jens Lehmann <Jens.Lehmann@web.de>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Marc Branchaud <marcnarc@xiplink.com>
Subject: [PATCH v3 0/7] Teach fetch/pull the on-demand mode and make it the default
Date: Sun, 06 Mar 2011 23:09:32 +0100 [thread overview]
Message-ID: <4D74061C.5050908@web.de> (raw)
Here is v3 of this patch series. Changes to v2 are:
*) Changed some documentation texts as proposed by Marc
*) Renamed the "--submodule-default" option to "--recurse-submodules-default"
*) Fixed some typos in the BUGS section
Jens Lehmann (7):
fetch/pull: recurse into submodules when necessary
fetch/pull: Add the 'on-demand' value to the --recurse-submodules
option
config: teach the fetch.recurseSubmodules option the 'on-demand'
value
Submodules: Add 'on-demand' value for the 'fetchRecurseSubmodule'
option
fetch/pull: Don't recurse into a submodule when commits are already
present
submodule update: Don't fetch when the submodule commit is already
present
fetch/pull: Describe --recurse-submodule restrictions in the BUGS
section
Documentation/config.txt | 12 ++-
Documentation/fetch-options.txt | 25 ++++-
Documentation/git-fetch.txt | 9 ++
Documentation/git-pull.txt | 11 ++-
Documentation/gitmodules.txt | 4 +-
builtin/fetch.c | 48 ++++++--
git-pull.sh | 3 +
git-submodule.sh | 5 +-
submodule.c | 152 +++++++++++++++++++++--
submodule.h | 11 ++-
t/t5526-fetch-submodules.sh | 255 +++++++++++++++++++++++++++++++++++++++
t/t7403-submodule-sync.sh | 2 +-
t/t7406-submodule-update.sh | 20 +++
13 files changed, 520 insertions(+), 37 deletions(-)
--
1.7.4.1.300.g29eea0
next reply other threads:[~2011-03-06 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 22:09 Jens Lehmann [this message]
2011-03-06 22:10 ` [PATCH v3 1/7] fetch/pull: recurse into submodules when necessary Jens Lehmann
2011-03-06 22:11 ` [PATCH v3 2/7] fetch/pull: Add the 'on-demand' value to the --recurse-submodules option Jens Lehmann
2011-03-06 22:11 ` [PATCH v3 3/7] config: teach the fetch.recurseSubmodules option the 'on-demand' value Jens Lehmann
2011-03-06 22:12 ` [PATCH v3 4/7] Submodules: Add 'on-demand' value for the 'fetchRecurseSubmodule' option Jens Lehmann
2011-03-06 22:12 ` [PATCH v3 5/7] fetch/pull: Don't recurse into a submodule when commits are already present Jens Lehmann
2011-03-06 22:13 ` [PATCH v3 6/7] submodule update: Don't fetch when the submodule commit is " Jens Lehmann
2011-03-06 22:14 ` [PATCH v3 7/7] fetch/pull: Describe --recurse-submodule restrictions in the BUGS section 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D74061C.5050908@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=marcnarc@xiplink.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 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.