On Saturday 10 October 2009, bill lam wrote: > On Fri, 09 Oct 2009, Johannes Sixt wrote: > > bill lam schrieb: > > > I have two git repos, no branches. > > > > > > repo 1. > > > emptyrootcommit -- A ... M > > > > > > repo 2. > > > emptyrootcommit -- N ... Z > > > > > > N was evolved from M but the time gap is large, how can I combine > > > them into one repo > > > > > > emptyrootcommit -- A ... M -- N ... Z > > > > > > so that snapshots N .. Z will not be changed. > > > > $ echo $(git rev-parse N) $(git rev-parse M) >> .git/info/grafts > > $ git filter-branch --tag-name-filter cat -- --all --not M > > > > i.e. you graft the older history right before the younger history, then > > you use git filter-branch to rewrite the parentship of the younger > > commits. > > Thanks, graft is new to me. I tested it works but it needs first issue > git fetch /path/to/repo1 > within repo2 to fetch tip M from repo1 into repo2, is it correct? > > If I also want to fetch also all objects from repo1, what will the > command to do it. Maybe you should do something like: $ git remote add repo1 /path/to/repo1 $ git fetch repo1 The fetch command should output something like: remote: Counting objects: 423, done. remote: Compressing objects: 100% (149/149), done. remote: Total 363 (delta 276), reused 298 (delta 213) Receiving objects: 100% (363/363), 136.65 KiB, done. Resolving deltas: 100% (276/276), completed with 29 local objects. >From /path/to/repo1 * [new branch] branch1 -> repo1/branch1 * [new branch] branch2 -> repo1/branch2 So the branches in repo1 will be available in repo2 as remote/repo1/branch1, remote/repo1/branch2, ... > Christian Couder also mentioned the git-replace command, how to stitch > with it? First you need to create a commit that will replace commit N, let's call it N' and after that you can use "git replace N N'". So the complex part is to create N'. You want N' to have the same content as N but to have M as parent. So you could do something like the following: (We suppose that commits A to M are in branch1 and that you are in the root directory of your repo2 working directory.) $ git checkout -b repo1-branch1 remote/repo1/branch1 $ git checkout N -- . $ export GIT_AUTHOR_NAME=<author name of commit N> $ export GIT_AUTHOR_EMAIL=<author email of commit N> $ export GIT_AUTHOR_DATE=<date of commit N> $ git commit -a And then use the commit message from commit N, and maybe also say in the commit message that it is replacement commit made to link repo1 with repo2 or something like that. At this step you have created N' and you should make sure that it is exactly what you want. It should point to the same tree as N, it should have M as parent, ... If everything is ok then you can use: $ git replace N HEAD And you should be done. Regards, Christian. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html