From: Mark Levedahl <mlevedahl@gmail.com>
To: Jacob Helwig <jacob.helwig@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] submodule: Improve handling of relative submodule URLs.
Date: Thu, 25 Feb 2010 21:03:50 -0500 [thread overview]
Message-ID: <4B872C06.50502@gmail.com> (raw)
In-Reply-To: <1267126109-14638-1-git-send-email-jacob.helwig@gmail.com>
On 02/25/2010 02:28 PM, Jacob Helwig wrote:
> Relative URLs only worked with<proto>://<host>/<location> style URLs, and
> would break when cloning a repository using<user>@<host>:<location> (scp)
> style "URL"s.
>
> When a submodule's URL was set to "../submodule.git", and the repository
> using it was cloned from "git@example.com:repo.git", git would try to
> clone the submodule from "git@example.com:repo.git/submodule.git", which
> would not likely work.
>
My solution for this has been to always give the full path, possibly using ~
e.g., git@example.com:~/repo.git
and as that works fine, I'm indifferent to this proposed change.
Mark
prev parent reply other threads:[~2010-02-26 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 19:28 [PATCH] submodule: Improve handling of relative submodule URLs Jacob Helwig
2010-02-26 2:03 ` Mark Levedahl [this message]
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=4B872C06.50502@gmail.com \
--to=mlevedahl@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacob.helwig@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.
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).