git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Location-agnostic submodules

From
PTPierre Thierry <pierre@nothos.net>
Date
Apr 30, 2012, 22:02 UTC
Message-ID
<20120430220244.GL22827@pape.arcanes.fr.eu.org>
In-Reply-To
<CABURp0qA9hK1fBd3rmLG61ErpbbzrcxO=AAmFOsoxjt=ozu09Q@mail.gmail.com>
Scribit Phil Hord dies 30/04/2012 hora 16:39:
Show 5 quoted lines
> Maybe something like this:
>     [submodule "foo"]
>         path = foo-mod
>         url = ../foo ../foo-alternate
> https://someplace.com/git/foo.git  https://kernel.org/git/foo

<rant>That is typically the kind of occasion when I wish every config file were sexprs...</rant>

> But if one of them lags behind the others by a day or even an hour,
> then you may have gitlinks in your superproject which have not made
> it into the lagging mirror yet.  And this will cause problems.

I see your point, but what if your only repository is lagging behind? I.e. in what way is it worse than now?

> Moreover, each time you clone the repository you may get different
> results.  This would be confusing.

Again, I fail to see the difference with the current state. If the commit is specified, you will always get the same results, now or with my suggested addition.

> I don't think there is any need for a new 'clone' command since the
> clone porcelain already understands submodules.

What do you mean? When I clone a repo with submodules, they are not cloned as well.

-- 
pierre@nothos.net
OpenPGP 0xD9D50D8A
Previous: Phil HordNext: Phil Hord
Message 3 of 8 in “Location-agnostic submodules”
  1. Pierre ThierryApr 27, 2012
  2. Phil HordApr 30, 2012
  3. Pierre ThierryApr 30, 2012
  4. Phil HordMay 1, 2012
  5. Philip OakleyMay 1, 2012
  6. Junio C HamanoMay 1, 2012
  7. Philip OakleyMay 1, 2012
  8. Heiko VoigtMay 2, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.