From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2011, #02; Sun, 20)
Date: Sun, 20 Mar 2011 21:43:11 +0100 [thread overview]
Message-ID: <4D8666DF.3050401@web.de> (raw)
In-Reply-To: <7vy649vah1.fsf@alter.siamese.dyndns.org>
Am 20.03.2011 20:49, schrieb Junio C Hamano:
> * jl/submodule-fetch-on-demand (2011-03-06) 7 commits
> - fetch/pull: Describe --recurse-submodule restrictions in the BUGS section
> - submodule update: Don't fetch when the submodule commit is already present
> - fetch/pull: Don't recurse into a submodule when commits are already present
> - Submodules: Add 'on-demand' value for the 'fetchRecurseSubmodule' option
> - config: teach the fetch.recurseSubmodules option the 'on-demand' value
> - fetch/pull: Add the 'on-demand' value to the --recurse-submodules option
> - fetch/pull: recurse into submodules when necessary
>
> Is this ready to move forward?
I'm not aware of any issues with that series, so I'd say yes. (The change in
behavior and that we support disconnected operation for submodules way better
than before should of course be mentioned in the release notes)
next prev parent reply other threads:[~2011-03-20 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 19:49 What's cooking in git.git (Mar 2011, #02; Sun, 20) Junio C Hamano
2011-03-20 20:43 ` Jens Lehmann [this message]
2011-03-20 21:06 ` Junio C Hamano
2011-03-20 21:22 ` Junio C Hamano
2011-03-20 21:36 ` Matthieu Moy
2011-03-21 0:06 ` Junio C Hamano
2011-03-21 11:16 ` Jeff King
2011-03-21 14:28 ` Junio C Hamano
2011-03-23 0:02 ` [PATCH] add: make "add -u/-A" update full tree without pathspec Junio C Hamano
2011-03-23 5:17 ` [PATCH] add: make "add -u/-A" update full tree without pathspec (step 2) Junio C Hamano
2011-03-23 5:19 ` [PATCH] add: make "add -u/-A" update full tree without pathspec (step 3) Junio C Hamano
2011-03-23 14:02 ` Nguyen Thai Ngoc Duy
2011-03-23 15:54 ` Junio C Hamano
2011-03-22 10:57 ` What's cooking in git.git (Mar 2011, #02; Sun, 20) Ævar Arnfjörð Bjarmason
2011-03-22 18:00 ` Junio C Hamano
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=4D8666DF.3050401@web.de \
--to=jens.lehmann@web.de \
--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).