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

Vendor-Branch setup

From
ASAdrian Stern <adrian.stern@unchained.ch>
Date
Oct 8, 2014, 14:07 UTC
Message-ID
<CAOHZ5L4aAT0vYfJ4g=5NmED9=nWyHS1ATf+15Y060uiz=CtkRQ@mail.gmail.com>
Hi

I have a Vendro-Branch setup where i store the official code in my own repository. Next to that i have a Delta-Branch where i store only the changed files different to the Vendor-Branch.

I have two problems with this setup:

1) When updating the Vendor-Branch (File A, B, C), the file A which is also present in the Delta-Branch, is not automatically updated in Delta. I cannot merge Vendor into Delta because thousands of other files would be added thus destroying the purpos of the Delta branch. Checking out Delta after updating Vendor will load the file from Delta. Can't i just merge the files already present in Delta from Vendor to Delta?

2) After upgrading Vendor and merging Delta to Vendor older files in Delta get ignored and not Merged. File A for example is newer in Vendor, but i need the changes from Delta. -X theirs does not work eigther. What i want is the merge-window.

Merge Strategy "theirs" does not work. I get "Already up-to-date" each time.

Any sugestions how i could get this to work? Or maybe there is a more logical setup?

Regards,

Adrian Stern unchained - web solutions

adrian.stern@unchained.ch +41 79 292 83 47

Next: Sergey Organov
Message 1 of 2 in “Vendor-Branch setup”
  1. Adrian SternOct 8, 2014
  2. Sergey OrganovOct 8, 2014

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.