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

Re: git file sharing/versioning.

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Jan 5, 2010, 20:10 UTC
Message-ID
<20100105201038.GA12942@vidovic>
In-Reply-To
<1262580426.9041.21.camel@ams.xobas.net>
The 04/01/10, Bas Driessen wrote:
Show 7 quoted lines
> I have a project where I have 2 trees with several hundreds of files.
> Let's call them tree1 and tree2. Only a handful of files in tree2 are
> different. What is the best way to set this up in GIT? Basically most
> files in tree2 should act as a symbolic link to tree1. So if the file
> changes in tree 1, it automatically changes in tree 2. Obviously, I
> don't want to store everything double. Branching does not appear to be
> an option as changes in tree1 would not be visible in the tree2 branch. 
Look at:
  git merge --help
  git rebase --help
  git cherry-pick --help
-- 
Nicolas Sebrecht
Previous: Bas DriessenNext: Nicolas Sebrecht
Message 2 of 3 in “Re: git file sharing/versioning.”
  1. Bas DriessenJan 4, 2010
  2. Nicolas SebrechtJan 5, 2010
  3. Nicolas SebrechtJan 6, 2010

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.