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

Beginner's question on how to use git for multiple parallel versions

From
CSChristian C. Schouten <info@zark3.net>
Date
Jan 4, 2010, 11:29 UTC
Message-ID
<F8CC469C9CCA415696101414EA997C0.MAI@sohosted19.com>
Hello all,

I&#8217;ve got a project that I want to do version management on with git but being a beginner in cvs/svn/dvcs etc. terminology I don&#8217;t know yet how to set it up. My project needs to exist as several parallel copies, i.e. there is a &#8220;main version&#8221; in which I do my development but it needs to end up being available as a couple of different configurations. For instance, say there is a file table.xml then this needs to contain different rows for versions A and B. Likewise, a file process.bpel needs to be named identical for each version but contain different content depending on whether it is distributed as version A or version B. Any changes made in non-version specific files should be visible in all copies, but changes made to version-specific files need to remain isolated to that particular version.

I read about branching, merging, rebasing and cherry-picking commits but I don&#8217;t get it yet. Can anyone enlighten me on how I should approach this in a way that I can maintain easily throughout future development for my situation?

Thanks in advance for any pointers,
Best,
Chris
Next: Bill Lear
Message 1 of 5 in “Beginner's question on how to use git for multiple parallel versions”
  1. Christian C. SchoutenJan 4, 2010
  2. Bill LearJan 4, 2010
  3. Christian C. SchoutenJan 4, 2010
  4. Bill LearJan 4, 2010
  5. Dmitry PotapovJan 4, 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.