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

Partial tree export and merging

From
HVHeiko Voigt <heiko.voigt@mahr.de>
Date
Sep 24, 2008, 13:58 UTC
Message-ID
<48DA476F.1070700@mahr.de>
In-Reply-To
<48D9FACB.20901@mahr.de>
Hallo,

I am currently facing a challenge for adding limited access to a git repository for the i18n and documentation (language) team. Our repository contains *.html and *.loc files which are located along with the code. The language team should not see the code. At the same time a developer using the full tree needs to be able to contribute to the i8n files.

To archieve this I would like to extract a repository that only contains the documentation and localization files which can be used by the i8n and doc team. This should be regularly merged into the development (with code) repository.

My idea of a solution would be to export patches only for the specific files and import them into a seperate empty repository/branch using git-format-patch and git-am. This seperate repository then itself then could be imported again with a normal merge operation. Has a anyone already solved such a problem or other ideas how to solve this ?

cheers Heiko
Next: Shawn O. Pearce
Message 1 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.