Hi, On Thu, 5 Jul 2007, Johannes Sixt wrote: > Sean Kelley wrote: > > > > I have a situation where we have a local GIT repository that is based > > on v2.6.17. We initially added the source tarball to an empty > > repository and then started applying changes to it. Looking back, > > that might not have been the best idea 400 commits later. > > That is possible using a graft: > > $ echo "$x $(git rev-parse v2.6.17^0)" >> .git/info/grafts > > where $x is the SHA1 of the first commit you made on top of the imported > tarball. Yes, this is also how I would do it. > This way you have spliced your history with Linus's history. (This is a > strictly _local_ matter! Every clone of your history must repeat the > game!) Now, here I disagree slightly. If you merge just once, subsequent merges will be possible even without that graft. So if you merge with some newer Linux version, all your cloners get the benefit. > Now, Linus will not be able to pull from your faked history because he > doesn't know about the graft. Except if you merge with a more recent version of Linux. However, I doubt that such a distant (in terms of time!) merge would appeal to Linus. I guess you have to rebase on top of Linus' version _anyway_. > In order to fix that, you can run git-filter-branch from current git's > master branch to rewrite your history: > > $ git filter-branch new-master v2.6.17..master > > Read the man page of git-filter-branch, and understand the implications > before you publish the result. This is a way to fix your history, yes. Note that filter-branch is not yet in an official release of Git, and so you either have to wait for 1.5.3, or you get filter-branch from git.git's "next" branch (just picking this one script should work fine, if you have at least 1.5.1 installed). Note that this rewrites the history, so all the disadvantages of rebasing with pulling apply here, too. But as stated above, I think you have to rebase eventually anyway, if you go for inclusion in Linus' tree. In that case, the filter-branch is unnecessary. Ciao, Dscho - 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
