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

Re: Site dependent repositories

From
ESEvan Shelhamer <shelhamer@imaginarynumber.net>
Date
Aug 21, 2011, 05:46 UTC
Message-ID
<loom.20110821T074112-429@post.gmane.org>
In-Reply-To
<4E507C05.2090700@sbcglobal.net>

Have you considered ignoring 'local' and 'extensions' and making each their own repositories?

A 'site' repository would contain the dir structure you described, and would have a .gitignore to ignore 'local' and 'extensions'. As these are now ignored by git, you are free to create a git repo in each dir that will be independent of the 'site' repo.

This way you would be able to push/pull 'site' repos without 'local' and 'extensions' being tracked or changed. However, you can still go into the 'local' and 'extensions' dirs and work with the git repos established for these directories.

This brings up the problem of keeping a given 'site' repo and its inner 'local' and 'extensions' repos in sync, but you could do this by coordinating pushs, pulls, and checkouts by a deploy script or something of that nature.

Previous: Andrew KellerNext: Jens Lehmann
Message 3 of 4 in “Site dependent repositories”
  1. Stewart A. BrownAug 21, 2011
  2. Andrew KellerAug 21, 2011
  3. Evan ShelhamerAug 21, 2011
  4. Jens LehmannAug 21, 2011

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.