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 5/7] fetch/pull: Don't recurse into a submodule when commits are already present
Date: Wed, 02 Mar 2011 11:08:17 -0500 [thread overview]
Message-ID: <4D6E6B71.2030800@xiplink.com> (raw)
In-Reply-To: <4D6D7B49.3030005@web.de>
As I said earlier, this patch should also tweak the documentation in
fetch-options.txt and config.txt.
In my suggested wording I used the phrase
... only recurse into a populated submodule when its superproject
retrieves a commit that updates the submodule's reference.
With this patch, that should now be
... only recurse into a populated submodule when its superproject
retrieves a commit that updates the submodule's reference to a
commit that isn't already in the local submodule clone.
M.
On 11-03-01 06:03 PM, Jens Lehmann wrote:
> When looking for submodules where new commits have been recorded in the
> superproject ignore those cases where the submodules commits are already
> present locally. This can happen e.g. when the submodule has been rewound
> to an earlier state. Then there is no need to fetch the submodule again
> as the commit recorded in the newly fetched superproject commit has
> already been fetched earlier into the submodule.
>
> Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
> ---
> submodule.c | 29 ++++++++++++++++++++++++++++-
> t/t5526-fetch-submodules.sh | 19 +++++++++++++++++++
> 2 files changed, 47 insertions(+), 1 deletions(-)
>
> diff --git a/submodule.c b/submodule.c
> index 3be6654..11e0ef5 100644
> --- a/submodule.c
> +++ b/submodule.c
> @@ -263,6 +263,33 @@ void set_config_fetch_recurse_submodules(int value)
> config_fetch_recurse_submodules = value;
> }
>
> +static int is_submodule_commit_present(const char *path, unsigned char sha1[20])
> +{
> + int is_present = 0;
> + if (!add_submodule_odb(path) && lookup_commit_reference(sha1)) {
> + /* Even if the submodule is checked out and the commit is
> + * present, make sure it is reachable from a ref. */
> + struct child_process cp;
> + const char *argv[] = {"rev-list", "-n", "1", NULL, "--not", "--all", NULL};
> + struct strbuf buf = STRBUF_INIT;
> +
> + argv[3] = sha1_to_hex(sha1);
> + memset(&cp, 0, sizeof(cp));
> + cp.argv = argv;
> + cp.env = local_repo_env;
> + cp.git_cmd = 1;
> + cp.no_stdin = 1;
> + cp.out = -1;
> + cp.dir = path;
> + if (!run_command(&cp) && !strbuf_read(&buf, cp.out, 1024))
> + is_present = 1;
> +
> + close(cp.out);
> + strbuf_release(&buf);
> + }
> + return is_present;
> +}
> +
> static void submodule_collect_changed_cb(struct diff_queue_struct *q,
> struct diff_options *options,
> void *data)
> @@ -280,7 +307,7 @@ static void submodule_collect_changed_cb(struct diff_queue_struct *q,
> * being moved around. */
> struct string_list_item *path;
> path = unsorted_string_list_lookup(&changed_submodule_paths, p->two->path);
> - if (!path)
> + if (!path && !is_submodule_commit_present(p->two->path, p->two->sha1))
> string_list_append(&changed_submodule_paths, xstrdup(p->two->path));
> } else {
> /* Submodule is new or was moved here */
> diff --git a/t/t5526-fetch-submodules.sh b/t/t5526-fetch-submodules.sh
> index 09701aa..3decfae 100755
> --- a/t/t5526-fetch-submodules.sh
> +++ b/t/t5526-fetch-submodules.sh
> @@ -428,4 +428,23 @@ test_expect_success "'submodule.<sub>.fetchRecurseSubmodules=on-demand' override
> test_cmp expect.err.2 actual.err
> '
>
> +test_expect_success "don't fetch submodule when newly recorded commits are already present" '
> + (
> + cd submodule &&
> + git checkout -q HEAD^^
> + ) &&
> + head1=$(git rev-parse --short HEAD) &&
> + git add submodule &&
> + git commit -m "submodule rewound" &&
> + head2=$(git rev-parse --short HEAD) &&
> + echo "From $pwd/." > expect.err &&
> + echo " $head1..$head2 master -> origin/master" >> expect.err &&
> + (
> + cd downstream &&
> + git fetch >../actual.out 2>../actual.err
> + ) &&
> + ! test -s actual.out &&
> + test_cmp expect.err actual.err
> +'
> +
> test_done
next prev parent reply other threads:[~2011-03-02 16:07 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
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 [this message]
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=4D6E6B71.2030800@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).