11 ms·

Still salty about them dropping mercurial support without providing any migration tools, and planning to just delete data without any archiving.

meritt 7y ago
I'm also salty. What's your plan? I'm either gonna migrate to git (and use a different host), or self-host something like hetapod.net
- bjoli 7y ago
  I went to sourcehut. I am very happy, but during the process I ended up actually having to learn a bit of git. Future projects will probably be git.
- patd 7y ago
  GitHub’s import feature worked well for me. You’re obviously going to lose the wiki, issues etc. But at least you’ll keep your repo history, branches, ...
- doubleunplussed 7y ago
  Yeah I'm moving to git and github. I always pteferred mercurial for what I maintain are good reasons not just of personal taste, but I've been swimming against the tide for too long and it makes sense to go with git and github. If github goes downhill, at least I'll be in good company next time!
compumike 7y ago
Also salty! For hg->git migration, https://github.com/frej/fast-export https://github.com/frej/fast-export worked smoothly for me. mkdir new-git-repo cd new-git-repo git init fast-export/hg-fast-export.sh -r ../path-to-old-hg-repo (probably want to translate .hgignore to .gitignore and commit it) git remote add origin git@path_to:git_server git push -u origin master git push --all
- johannes1234321 7y ago
  Yes, it is fairly easy to convert the repo, but 1) this afaik couldn't be done inside the BB project, so one would have had to create a new repo and lose bug history etc. 2) It's a trust thing. If BB kills repos once, who doesn't say they won't kill others tomorrow? 3) Comfort: Import to GitHub is a click away
michaelhoffman 7y ago
Same here. I don't love that they aren't going to support Mercurial anymore. But deleting all our existing projects without providing a path for us to migrate or archive? I can't trust them anymore.

meritt 7y ago

I'm also salty. What's your plan? I'm either gonna migrate to git (and use a different host), or self-host something like hetapod.net

bjoli 7y ago
I went to sourcehut. I am very happy, but during the process I ended up actually having to learn a bit of git. Future projects will probably be git.
patd 7y ago
GitHub’s import feature worked well for me. You’re obviously going to lose the wiki, issues etc. But at least you’ll keep your repo history, branches, ...
doubleunplussed 7y ago
Yeah I'm moving to git and github. I always pteferred mercurial for what I maintain are good reasons not just of personal taste, but I've been swimming against the tide for too long and it makes sense to go with git and github. If github goes downhill, at least I'll be in good company next time!

compumike 7y ago

Also salty! For hg->git migration, https://github.com/frej/fast-export https://github.com/frej/fast-export worked smoothly for me. mkdir new-git-repo cd new-git-repo git init fast-export/hg-fast-export.sh -r ../path-to-old-hg-repo (probably want to translate .hgignore to .gitignore and commit it) git remote add origin git@path_to:git_server git push -u origin master git push --all

johannes1234321 7y ago
Yes, it is fairly easy to convert the repo, but 1) this afaik couldn't be done inside the BB project, so one would have had to create a new repo and lose bug history etc. 2) It's a trust thing. If BB kills repos once, who doesn't say they won't kill others tomorrow? 3) Comfort: Import to GitHub is a click away

michaelhoffman 7y ago

Same here. I don't love that they aren't going to support Mercurial anymore. But deleting all our existing projects without providing a path for us to migrate or archive? I can't trust them anymore.