PyPy has moved to Git, GitHub | PyPy about pypy.org HOT 14 OPEN

Was gitlab considered? Could it be considered? Should be easier after the move to git.

from pypy.org.

We were on gitlab: foss.heptapod.net is a friendly fork of gitlab. The problem is the friction of interacting with other software packages when they all are located on github.

from pypy.org.

On reddit someone commented:

That process was likely a lot slower than it needed to be. You generally don't need to check out a git ref to operate on the ref itself, only if you actually really need to change your working tree.

Since the git notes add command works on the current HEAD, I needed to checkout each commit in turn and then add the note

git notes add works on the current HEAD.... by default. You can easily pass it an object id to avoid the checkout.

while read branch; do git checkout branches/$branch && git push origin branches/$branch; done < branches.txt

Same thing, you don't need to check out a ref to push it.

git push origin <branch>

You can even just push just a commit hash, just if you do you need to tell git to push it as a new head to the remote by explicitly stating the namespace:

git push origin <hash>:refs/heads/<branchname>

from pypy.org.

People who wish to continue to use Mercurial can use the same method below to push to GitHub.

I don't think this sentence alone will help people like me that are not very familiar with git. As far as I understand it, outside contributors on github must go through the process of making a clone on github, fetching a local copy, pushing some new commits in it, and using the github web interface to propose that as a pull request back to the main repo. Is there also very different approach starting with the mercurial copy of the repo somehow?

from pypy.org.

from pypy.org.

Thanks! So the best solution for me is probably just to check out the new pypy repo in the usual way with git and then submit patches as github issues, generated with the appropriate set of git diff options.

from pypy.org.

People who wish to continue to use Mercurial can use the same method below to push to GitHub.

Well, I may have misrepresented that. I meant "people who wish to convert their local Mercurial repo to Git". But truthfully it is probably easier to do git clone https://github.com/pypy/pypy than to convert the repo and get all the correct branches.

from pypy.org.

You should ask github to repack the pypy repo, because it's 2GB instead of the 200MB it could be after an aggressive repack or 400MB after a less aggressive repack. Presumably, you just pushed the result of git-remote-hg without a repack, and git-remote-hg isn't really great at creating tight packs.

from pypy.org.

@glandium: interesting suggestion! how would we do that? is that exposed in the UI or do you need to send an email to the right person?

from pypy.org.

Github an open source synonymous ? Guys, are you aware that GitHub itself isn't open source ? What a joke.

from pypy.org.

You should ask github to repack the pypy repo

Thanks @glandium. I reached out to github support and they did something, now the repo is much smaller.

from pypy.org.