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

Re: Importing Bzr revisions

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 23, 2009, 08:06 UTC
Message-ID
<7veiwo8xz7.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<90DBD254-1810-4B11-AA9F-C5661A028FA5@gmail.com>
David Reitter <david.reitter@gmail.com> writes:
> Suppose I have a bzr branch that has been converted (somehow) to a git
> branch, is it then possible to merge new revisions from the bzr branch
> into the git one?
It entirely depends on how that "somehow" goes.

If that "somehow" procedure performs a reliably reproducible conversion (i.e. not only it will produce the identical git history when you feed the same bzr history to the procedure twice, but it will produce the identical git history followed by new history if you feed the bzr history after new commits are added to the bzr history), you should be able to re-convert the updated bzr history to git and merge the result with the result of the earlier conversion. The re-conversion process may not even have to be a whole re-conversion; it could be incremental. But that is entirely up to the quality of the conversion "somehow" procedure implements.

Previous: David ReitterNext: David Reitter
Message 2 of 11 in “Importing Bzr revisions”
  1. David ReitterMar 23, 2009
  2. Junio C HamanoMar 23, 2009
  3. David ReitterMar 23, 2009
  4. David ReitterMar 23, 2009
  5. Shawn O. PearceMar 23, 2009
  6. Teemu LikonenMar 23, 2009
  7. David ReitterMar 26, 2009
  8. Pieter de BieMar 23, 2009
  9. David ReitterMar 23, 2009
  10. Pieter de BieMar 23, 2009
  11. David ReitterMar 23, 2009

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.