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

Repository usage

From
NKNikola Knežević <nikkne@gmx.ch>
Date
May 28, 2008, 21:51 UTC
Message-ID
<21512C1E-EEA3-43C1-9099-78563B64DC44@gmx.ch>

Hi all, I have a question related on how to use VCS's, and git in particular.

So, the situation is this: we were using project called Mace (framework for building dist. systems). Up until 1yr ago, it was a monolithic project, contained in one SVN repository. We build a lot of changes on top of original code, but we never synchronized with the main repository. Then, the developers decided to split the repository into 2 parts - public and private. They also switched to CMake, so it was possible to use cmake to build both public and private part in one invocation (although they were in separate directories). IHMO, their idea was quite stupid! Since we now need to synchronize with their code, I don't know what to do... Our code relies on parts of public and private, and build order is also important, so I can't update only one part.

Before I describe what I need, if I use /\ for set intersection, and \/ for union, situation is like this: public/\private = mostly makefiles, public\/private == old mace

Since I need both parts, their complete union, and I need to update to latest code (a lot of performance&bug fixes is there), I thought to use git-svn to create one branch for public, one for private, and then merge both to the same branch. Both public and private contain the same layout, but there are different files in directories. Is this even possible? Is there any better solution?

Thanks, and sorry if I've missed the right mailing list... Nikola

Message 1 of 1 in “Repository usage”
  1. Nikola KneževićMay 28, 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.