Re: [CEDET-devel] transplant revisions between unrelated projects
Brought to you by:
zappo
From: Stefan M. <mo...@ir...> - 2012-04-30 14:35:14
|
>>> You can find the code here: >>> https://launchpad.net/bzr-tp/trunk >>> This will give some more details on how to use it: >>> bzr help transplant >> Could you describe (or point to a description) of what it actually does? > Could be seen like an inter-project merge tool, where history is kept > (including merges), as long as the "transplanted" revisions affect > files identified as "transplantable". > For example, emacs->cedet synchronization would transplant files > "lisp/emacs-lisp/eieio\(.*\).el" from emacs into > "lisp/eieio/eieio\1.el" in cedet, where cedet controls what to > transplant and when (transplant metadata is committed into the cedet > branch): I understand that, but I don't understand how it does it. It seems like it works a bit like a "rebase". So, what does "history is kept" mean exactly? Will a "bzr tp-from" (once "tp-from-finish"ed) appear as a merge in the DAG? Stefan |