On Wed, Apr 19, 2017 at 7:40 AM, Kacper Kowalik
I don't know how to do that :) What we are mapping to git branches are hg bookmarks, and you can't have bookmark matching named branch:
$ hg bookmark yt-2.x abort: a bookmark cannot have the name of an existing branch
Cheers, Kacper
I created a pull request that should fix this issue: https://github.com/yt-project/fido-prhandler/pull/1 In addition this pull request sets the mirror target to the final repo location, in expectation of getting approval in this thread.
Cheers, Kacper
Our mirror bot uses hg-git, and the converted repo hg-git produces
isn't
necessarily perfect. In particular, two issues have come up:
* Since git is more selective than mercurial about e-mail and
username
formatting, there are a number of commits associated with dummy e-mail addresses like none@none
* Since we do most of our development on a branch named "yt" (not "default" as is typical of mercurial repos) almost every commit in our history has a comment in the git commit message recording that it hapenned on the "yt" or "stable" branch. This makes it possible to round-trip from hg to git and back to hg, but it's also some extra noise in every single commit message.
We could in principle ameliorate these issues by using something besides hg-git to do the conversion or by modifying hg-git to avoid these issues. The former options will lose the nice property of being able to round-trip and for others to independently export work from their forks. The latter option will require us to modify hg-git and waiting for upstream hg-git to review our changes, which might take a while, or telling everyone to use a hacked version of hg-git.
Personally, I don't think either of those options are worth the hassle for what to me are minor annoyances. I think I've also ameliorated the username/e-mail ambiguity in the converted history by adding a .mailmap file to the repo:
https://bitbucket.org/yt_analysis/yt/pull-requests/2582
In addition, the mirroring process we have now seems to work well, so just renaming the yt-test repo and calling the conversion final avoids a bunch more work which will block further progress on the conversion.
What do you all think? It would be great to get people's +/-1 on renaming yt-test to yt on github.com/yt-project.
Once we have a final repo name we will be able to start porting tooling like the website generator without worrying about the name or content of the final repo changing.
-Nathan
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org