Hi Christoph, thanks for the hint. I considered something similar to have GIT and HG in parallel. But it made the impression of generating more work. This is just a guts feeling. Maybe I reconsider if writing that tutorial turns out to be too weird to be understood by a majority.:D
Migrating from GitHub to Bitbucket is of course possible. However I agree with most hg repo-owners on Bitbucket that their non existing migration support shouldn't be supported. I hope GitHub is more reliable in the future. Oliver - > Gesendet: Donnerstag, 12. September 2019 um 07:48 Uhr > Von: "Christoph Moench-Tegeder" <[email protected]> > An: [email protected] > Betreff: Re: [Qlandkartegt-users] Release V1.13.2 and how to proceed in the > future > > ## Oliver Eichler ([email protected]): > > > Now to a less pleasant topic: > > Some of might have heard that Bitbucket drops Mercurial support. Well > > I am not particular a huge fan of Mercurial but compared to GIT it's > > way more easy to use. Plus it comes with a nice GUI tool TortoisHg. > > This makes it easy even for no full time software developers to use > > it and to contribute. That's why I favor it over GIT for a project > > like QMapShack. > > For what it's worth, there's https://hg-git.github.io/, which might > make the migration much easier and help conserve workflows for > those who want to stay with mercurial. (I'm not getting into another > argument over version control systems, as I've seen way too many of > them over the years). Perhaps it's even possible to use this to just > push back everything into bitbucket's git and keep everything else? > > Regards, > Christoph > > -- > Spare Space > > > _______________________________________________ > Qlandkartegt-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
