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

Re: Partial tree export and merging

From
HVHeiko Voigt <heiko.voigt@mahr.de>
Date
Sep 24, 2008, 15:05 UTC
Message-ID
<48DA5737.4030909@mahr.de>
In-Reply-To
<20080924143945.GN3669@spearce.org>
Shawn O. Pearce schrieb:
> Once the history is split into a new "doc+html" repository have
> developers _only_ edit the docs/html in the doc+html repository,
> don't make more edits in the source code repository.

The problem with committing into 2 repositories (only merging from one side) is that the docs/html also contain localization files which make it hard to work/test the code because localization strings are initially added by the developers. They would then have to change in the 2nd repo and pull for testing.

> You can use git-submodule or git-merge with the subtree strategy
> to pull changes from the doc+html repository into the main source
> repository.

Would git submodule work with this kind of layout? Same folders containing different files. I thought submodules only work with subdirectories which are itself a git repo.

cheers Heiko
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 3 of 7 in “Partial tree export and merging”
  1. Heiko VoigtSep 24, 2008
  2. Shawn O. PearceSep 24, 2008
  3. Heiko VoigtSep 24, 2008
  4. Shawn O. PearceSep 24, 2008
  5. Nguyen Thai Ngoc DuySep 24, 2008
  6. Heiko VoigtSep 25, 2008
  7. Nguyen Thai Ngoc DuySep 25, 2008

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.