> * This repo does not have an inbound branch like my mirror did, so if you > want a commit which is on mozilla-inbound but not on mozilla-central yet, I > guess you should wait until it gets merged to mozilla-central.
Although that repository doesn't have an inbound branch, there is a separate integration-mozilla-inbound repository, whose master branch corresponds to m-i. https://github.com/mozilla/integration-mozilla-inbound/ It's kind of annoying that you have to explicitly fetch from both remotes, but in the grand scheme of things, it's not too bad. > * This repo is created by RelEng by a direct conversion of the mercurial > repository to git, which means that there is no CVS history for you to use. This was /the/ killer feature of Ehsan's mirror, and I'm hopeful that releng will include CVS history in their mirror soon (at the cost of forcing us to rebase all our branches once again, of course). In the meantime, it's not too hard to attach CVS history to the releng repository, locally. Pull Ehsan's repository into your new releng repository. Then do $ git replace 2514a423 215f52d0 (If you examine those hashes, you should see that 215f52d0 is the last CVS cset from Ehsan's repository, while 2514a423 is the first commit in the releng repository. So we're effectively replacing "Free The Distributed Lizard" with the last CVS commit.) I've only been using this for a day, so caveat emptor, but it seems to work. Crucially, the git replace command will not change any of your hashes. You can even push and pull these replace revs, if that sort of thing floats your boat. According to [1], the magic commands are git push 'refs/replace/*' git fetch 'refs/replace/*:refs/replace/*' It's not great, but it's better than not having CVS history! Happy hacking, -Justin [1] http://git.661346.n2.nabble.com/What-s-the-best-way-to-push-fetch-replace-refs-td7137925.html On Thu, Sep 13, 2012 at 6:30 PM, David Humphrey <david.humph...@senecacollege.ca> wrote: > Thanks for your work, Ehsan, it's really appreciated. > > Can we file a bug on this and not have it be something literally off the > side of your desk? Too many of us depend on it now to not see this through, > and if you can't get it, we need to find another solution soon. > > Dave > > > On 12-09-13 6:24 PM, Ehsan Akhgari wrote: >> >> On 12-09-13 6:18 PM, Ralph Giles wrote: >>>> >>>> * This repo is created by RelEng by a direct conversion of the mercurial >>>> repository to git, which means that there is no CVS history for you to >>>> use. >>> >>> >>> You you understand why this repo doesn't have the same problem with the >>> ionmonkey merge? >> >> >> I'm reasonably certain that I hit a bug in hg-git. I've tried their tip >> version but that still doesn't fix it. I don't know the details of the bug >> unfortunately (which prevents me from fixing it!), but I have no reason to >> believe that it has anything to do with my setup, so I'm pretty sure that >> the other repo will hit the same problem sooner or later. Which means that >> it's really a good idea for the maintainers of that repo to try to figure >> out what happened with my mirror before this bug breaks their setup. :-) >> >> Cheers, >> Ehsan >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
