On 9/3/13 8:25 AM, Ehsan Akhgari wrote:
5. Is the git-mapfile generated from the conversion scrips available
somewhere? (Mine is currently available here:
http://git.mozilla.org/?p=users/eakhg...@mozilla.com/mozilla-history-tools.git;a=history;f=updates/git-mapfile;h=5c8ecf4bf1d7339ad1dff1ea4ab62a712da2fb6c;hb=HEAD
)
6. Do you have any plans for how we're going to approach the problem of
migrating the current git mirror with beagle? Specifically, I think we
need to:
a) Figure out how github deals with a repository being deleted/recreated,
would that break people's forks, stars, etc.?
b) Are there any alternative solutions in replacing all of the
branches/tags under mozilla/mozilla-central with the new repo?
c) What is the developer work flow going to look like in rebasing the local
branches once the move has been completed?
Publishing the mapfile as a raw file and possibly as a simple lookup
service would help here. I'd love to integrate this mapfile into my
"mozext" Mercurial extension [1] so things like |hg log| can easily
display the corresponding Git commits. Publishing the mapping of old Git
SHA-1's to new SHA-1's also enables easy transition/rebasing to the new
SHA-1's. tl;dr publish all the data publicly and good things happen.
[1] https://hg.mozilla.org/users/gszorc_mozilla.com/hgext-gecko-dev
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
