From: Peter Kaestle <peter.kaestle@nokia.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Stefan Beller <sbeller@google.com>
Cc: peter.kaestle@nokia.com
Subject: [REGRESSION FIX 0/2] Handling regression introduced by a62387b
Date: Tue, 3 Nov 2020 15:23:17 +0100 [thread overview]
Message-ID: <1604413399-63090-1-git-send-email-peter.kaestle@nokia.com> (raw)
These two patches introduce a test case which triggers a regression
introduced by a62387b3fc9f5aeeb04a2db278121d33a9caafa7 and a revert of
the commit introducing the issue.
The test case reproduces following scenario:
Repository setup:
superproject/middle_repo/inner_repo
Person A and B have both a clone of it, while Person B is not working
with the inner_repo and thus does not have it initialized in his working
copy.
Now person A does a change to the inner_repo and propagates it through
the middle_repo and the superproject.
Once person A pushed the changes, a "git fetch" on superproject level of
person B will return with error saying:
Could not access submodule 'inner_repo'
Errors during submodule fetch:
middle_repo
The revert was my quick approach to fix it. However as I'm not fully
aware of what the idea was behind handling the submodules inside
.git/modules instead of the worktree, I don't know whether this is the
best solution. Maybe rethinking the whole get_next_submodule()
algorithm or simply fixing the is_empty_dir() to use the worktree path
will be a better solution.
best regards,
--peter;
Peter Kaestle (2):
submodules: test for fetch of non-init subsub-repo
Revert "submodule.c: fetch in submodules git directory instead of in
worktree"
submodule.c | 14 ++++----------
t/t5526-fetch-submodules.sh | 38 ++++++++++++++++++++++++++++++++++++++
2 files changed, 42 insertions(+), 10 deletions(-)
--
2.6.2
next reply other threads:[~2020-11-03 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 14:23 Peter Kaestle [this message]
2020-11-03 14:23 ` [REGRESSION FIX 1/2] submodules: test for fetch of non-init subsub-repo Peter Kaestle
2020-11-03 14:23 ` [REGRESSION FIX 2/2] Revert "submodule.c: fetch in submodules git directory instead of in worktree" Peter Kaestle
2020-11-09 8:33 ` [RFC 0/2] Handling regression introduced by a62387b Peter Kaestle
2020-11-09 8:33 ` [RFC 1/2] submodules: test for fetch of non-init subsub-repo Peter Kaestle
2020-11-09 17:52 ` Junio C Hamano
2020-11-11 12:45 ` Peter Kästle
2020-11-11 17:22 ` Philip Oakley
2020-11-12 16:00 ` [RFCv2] submodules: fix of regression on fetching " Peter Kaestle
2020-11-11 17:35 ` [RFC 1/2] submodules: test for fetch " Philippe Blain
2020-11-11 19:27 ` Junio C Hamano
2020-11-11 19:24 ` Philippe Blain
2020-11-09 8:33 ` [RFC 2/2] Revert "submodule.c: fetch in submodules git directory instead of in worktree" Peter Kaestle
2020-11-10 15:08 ` Johannes Schindelin
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=1604413399-63090-1-git-send-email-peter.kaestle@nokia.com \
--to=peter.kaestle@nokia.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).