Wouldn't we need to continually mirror git.webkit.org to github as well? I presume github is mirroring directly from svn right now. I'd think the out-of-sync issue would simply occur again unless we started to mirror git. webkit.org to github instead of svn to github.
I don't know what all Git takes into account when creating the sha1 outside of content, tree and commit meta data, so I'm unsure if doing this git. webkit.org => github forced push would mean that future svn commits - being mirrored to both repos in parallel - would result in identical sha1 hashes going forward...? Jarred On Wed, Apr 18, 2012 at 6:53 AM, Shezan Baig <shezbaig...@gmail.com> wrote: > Hi WebKit, > > I've been using a fork of the following repo: > https://github.com/WebKit/webkit > > However, yesterday there was discussion on #webkit that the SHA-1 > checksums on this repo are different from repo at git.webkit.org, which > means folks working on both need to have both versions checked out. > > I believe the answer to this problem is in: > http://help.github.com/move-a-repo/ > > (look at the last section titled "Manual clone and push") > > Anyone in the "WebKit" organization on https://github.com/WebKit should > be able to push this. Once this is pushed, we can retire the existing repo > on github. This means the existing forks will be unusable, but I think it > will be good to do this earlier rather than later, so we just have "one" > repo, and this will make it easier for existing git.webkit.org users to > switch to github. > > Thanks, > -shez- > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev