From: Yaroslav Halchenko <yoh@onerussian.com>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Gurus hangout <git@vger.kernel.org>,
Benjamin Poldrack <benjaminpoldrack@gmail.com>,
Joey Hess <id@joeyh.name>, Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: problems serving non-bare repos with submodules over http
Date: Wed, 20 Apr 2016 23:14:26 -0400 [thread overview]
Message-ID: <20160421031426.GY23764@onerussian.com> (raw)
In-Reply-To: <CAGZ79kbyDuu8hUQXOUNmDLyO88GOi3kqSzsc0UfgzwAL9peZHg@mail.gmail.com>
NB Thank you for the lively discussion!
On Wed, 20 Apr 2016, Stefan Beller wrote:
> >> So currently the protocol doesn't allow to even specify the submodules
> >> directories.
> > Depends on what you exactly mean by "the protocol", but the
> > networking protocol is about accessing a single repository. It is
> > up to you to decide where to go next after learning what you can
> > learn from the result, typically by following what appears in
> > the .gitmodules file.
> Right. But the .gitmodules file is not sufficient.
why?
> >...<
> I think on a hosting site they could even coexist when having the
> layout as above.
> top.git/
> top.git/refs/{heads,tags,...}/...
> top.git/objects/...
> sub.git/
> sub.git/refs/{heads,tags,...}/...
> sub.git/objects/...
> # the following only exist in non bare:
> top.git/modules/sub.git/
> top.git/modules/sub.git/refs/{heads,tags,...}/...
> top.git/modules/sub.git/objects/...
> The later files would be more reflective of what you *really*
> want if you clone from top.git.
may be there is no need for assumptions and .gitmodules should be
sufficient?
- absolute url in .gitmodules provides absolute URL/path to the
submodule of interest, regardless either submodule is present in
originating repository as updated submodule. Either cloning it
instead of original repository would be more efficient is already a
heuristic which might fail miserably (may be I have a faster
connection to the original repository pointed by the absolute
url than to this particular repository)
- relative url in .gitmodules provides relative location to the location
of the "top" repository, and that is only when that submodule "absolute"
url should be resolved relative to the one of the "top" repository
NB I will consider it a separate issue either relative paths
without '../' prefix are having any sense in bare repositories.
or have I missed the point?
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
next prev parent reply other threads:[~2016-04-21 3:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 15:22 problems serving non-bare repos with submodules over http Yaroslav Halchenko
2016-04-20 16:14 ` Stefan Beller
2016-04-20 19:45 ` Yaroslav Halchenko
2016-04-20 19:51 ` Junio C Hamano
2016-04-20 21:05 ` Stefan Beller
2016-04-20 21:27 ` Junio C Hamano
2016-04-20 23:05 ` Stefan Beller
2016-04-21 3:14 ` Yaroslav Halchenko [this message]
2016-04-21 17:11 ` Stefan Beller
2016-04-21 17:45 ` Junio C Hamano
2016-04-21 17:48 ` Stefan Beller
2016-04-21 22:42 ` Jacob Keller
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=20160421031426.GY23764@onerussian.com \
--to=yoh@onerussian.com \
--cc=Jens.Lehmann@web.de \
--cc=benjaminpoldrack@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=id@joeyh.name \
--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.
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).