From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Jens.Lehmann@web.de,
Jon Seymour <jon.seymour@gmail.com>
Subject: [PATCH v4 0/2] submodule: fix handling of relative superproject origin URLs
Date: Thu, 24 May 2012 02:45:52 +1000 [thread overview]
Message-ID: <1337791554-31294-1-git-send-email-jon.seymour@gmail.com> (raw)
This series ensures that git submodule handles relative superproject origin URLs correctly.
Current behaviour:
* does not guarantee that the submodule.{name}.url property of the superproject is
always confgured with a valid path to the submodule's origin repo that is
relative to the working tree of the superproject.
* does not guarantee that the remote.origin.url property of the submodule is
always configured with a valid path to the submodule's origin repo that is
relative to the working tree of the submodule
* errors out (origin URL = foo) even though this is not strictly necessary.
These changes:
* guarantee that the configured paths are always valid relative paths
from the working tree of the repo containing to the configuration to the
origin repo of the described submodule.
Jon Seymour (2):
submodule: document handling of relative superproject origin URLs
submodule: fix handling of relative superproject origin URLs
git-submodule.sh | 17 ++++++++++--
t/t7400-submodule-basic.sh | 60 +++++++++++++++++++++++++++++++++++++++++++
t/t7403-submodule-sync.sh | 64 +++++++++++++++++++++++++++++++++++++++++++++-
3 files changed, 138 insertions(+), 3 deletions(-)
--
1.7.10.2.594.g24e850d
next reply other threads:[~2012-05-23 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 16:45 Jon Seymour [this message]
2012-05-23 16:45 ` [PATCH v4 1/2] submodule: document handling of relative superproject origin URLs Jon Seymour
2012-05-23 20:58 ` Jens Lehmann
2012-05-23 21:14 ` Junio C Hamano
2012-05-23 21:45 ` Jens Lehmann
2012-05-23 21:55 ` Jon Seymour
2012-05-23 16:45 ` [PATCH v4 2/2] submodule: fix " Jon Seymour
2012-05-23 21:50 ` Jens Lehmann
2012-05-23 22:17 ` Jon Seymour
2012-05-24 2:32 ` Jon Seymour
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=1337791554-31294-1-git-send-email-jon.seymour@gmail.com \
--to=jon.seymour@gmail.com \
--cc=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).