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

Re: How to combine git repos with similar code and keep all branches and tags?

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 14, 2015, 17:09 UTC
Message-ID
<vpqr3rm8wn6.fsf@anie.imag.fr>
In-Reply-To
<BBAA9EAE77388248BCAB045DA762C5A83EFE242F@EXBE01-ENSIM.ms.ensim.com>
Jose de Leon <jdeleon@ensim.com> writes:
Show 5 quoted lines
> For some unknown reason to me, our developers started a git project,
> called Ver1, this was the first version. Then sometime later, they
> created a new git repository called Ver2, the initial commit for Ver2
> was essentially a copy of the code in Ver1 from the master. They
> didn't clone it, they just copied the code at the latest point.

This is why "graft points" were created, and then superseeded by "git replace".

See http://git-scm.com/blog/2010/03/17/replace.html and http://git-scm.com/docs/git-replace

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Jose de LeonNext: Junio C Hamano
Message 2 of 5 in “How to combine git repos with similar code and keep all branches and tags?”
  1. Jose de LeonApr 14, 2015
  2. Matthieu MoyApr 14, 2015
  3. Junio C HamanoApr 14, 2015
  4. Max HornApr 14, 2015
  5. Jose de LeonApr 14, 2015

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.