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

Re: git multisite setup

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Nov 17, 2009, 00:50 UTC
Message-ID
<20091117005005.GC13074@vidovic>
In-Reply-To
<13f0168a0911161617o56757488n45328714fb1d3bea@mail.gmail.com>
[ Please, don't top-post nor whole quote. ]
The 16/11/09, Matt Di Pasquale wrote:
>                                       the specific git repos aren't
> coordinated to the generic one. but that's fine so far since i haven't
> had to jump around to different commits and the generic has stayed
> pretty much the same.

I'm not sure to understand exactly what kind of coordination you expect exactly (because you don't describe what you'd like that much), but submodule could be what you need, yes.

FMHO, the best way to check if you need it is to try it. For a good start, I guess you'll need to change your approach on "what depends of what". I think you should consider the _common_ part to be the _dependency_; as a consequence, it should be the submodule used in the other repositories. AFAIR, submodule was originaly designed to make our life easier with libraries. It may fit to your needs too but again, the best thing to do is to try.

-- 
Nicolas Sebrecht
Previous: Matt Di Pasquale
Message 4 of 4 in “git multisite setup”
  1. Matt Di PasqualeNov 16, 2009
  2. Nicolas SebrechtNov 17, 2009
  3. Matt Di PasqualeNov 17, 2009
  4. Nicolas SebrechtNov 17, 2009

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.