Mercurial support #147

@joubertredrat commented on GitHub (Dec 23, 2016):

SCM Manager supports mercurial too.

PS: Pesonally I prefer Fossil instead Mercurial.

@joubertredrat commented on GitHub (Dec 23, 2016): [SCM Manager](https://www.scm-manager.org) supports mercurial too. PS: Pesonally I prefer Fossil instead Mercurial.

GiteaMirror commented

@tboerger commented on GitHub (Dec 23, 2016):

I think it can be a big plus for gitea to support mercurial and bazaar, but the name of the project will be irritating and we need lots of abstractions

@tboerger commented on GitHub (Dec 23, 2016): I think it can be a big plus for gitea to support mercurial and bazaar, but the name of the project will be irritating and we need lots of abstractions

GiteaMirror commented

@joubertredrat commented on GitHub (Dec 23, 2016):

@tboerger sound be good?

"GMBFitea: Git, Mercurial, Bazaar, Fossil, All with a cup of tea". And true, will be necessary a lot of abstractions and see if golang support mercurial and bazaar API rerefence.

@joubertredrat commented on GitHub (Dec 23, 2016): @tboerger sound be good? "GMBFitea: Git, Mercurial, Bazaar, Fossil, All with a cup of tea". And true, will be necessary a lot of abstractions and see if golang support mercurial and bazaar API rerefence.

GiteaMirror commented

@tboerger commented on GitHub (Dec 23, 2016):

We are also wrapping just the git cli, so go bindings are not a hard requirement :)

@tboerger commented on GitHub (Dec 23, 2016): We are also wrapping just the git cli, so go bindings are not a hard requirement :)

GiteaMirror commented

@lunny commented on GitHub (Dec 23, 2016):

In a short term, this will not be consider I think.

@lunny commented on GitHub (Dec 23, 2016): In a short term, this will not be consider I think.

GiteaMirror commented

@strk commented on GitHub (Dec 24, 2016):

I also think this is outside the scope of Gitea

@strk commented on GitHub (Dec 24, 2016): I also think this is outside the scope of Gitea

GiteaMirror commented

@thibaultmeyer commented on GitHub (Dec 24, 2016):

The git and mercurial controls have practically the same behaviors. By example, the client SmartGit have the same UI for Mercurial and Git repos. It could make sens to become compatible with Mercurial.

@thibaultmeyer commented on GitHub (Dec 24, 2016): The git and mercurial controls have practically the same behaviors. By example, the client SmartGit have the same UI for Mercurial and Git repos. It could make sens to become compatible with Mercurial.

GiteaMirror commented

@stevenroose commented on GitHub (Dec 27, 2016):

It's even out of the scope of the name :D It's always good to have the choice, but I think it's more important to have a solid piece of software before adding non-core features...

@stevenroose commented on GitHub (Dec 27, 2016): It's even out of the scope of the name :D It's always good to have the choice, but I think it's more important to have a solid piece of software before adding non-core features...

GiteaMirror commented

@petrus-v commented on GitHub (Sep 27, 2018):

A bit of reading regarding Mercurial support on gitlab a POC was done to show that git/mercurial basic workflow are very closed.

@petrus-v commented on GitHub (Sep 27, 2018): A bit of reading regarding [Mercurial support on gitlab](https://gitlab.com/gitlab-org/gitlab-ce/issues/31600) a POC was done to show that git/mercurial basic workflow are very closed.

GiteaMirror commented

@Crystal-Lilith commented on GitHub (Mar 28, 2020):

Hello everyone, i am quite curious if hg support will eventually be implemented, do you think that it will be worth putting the effort into making it happen?

@Crystal-Lilith commented on GitHub (Mar 28, 2020): Hello everyone, i am quite curious if hg support will eventually be implemented, do you think that it will be worth putting the effort into making it happen?

GiteaMirror commented

@clarfonthey commented on GitHub (Jun 30, 2020):

I also want to voice support for allowing multiple VCS types. Honestly, there are still lots of systems out there that use VCS other than git and allowing users to mirror those repos without converting them to git would be great. IMHO, the best thing would be to abstract the git logic so that ultimately people could develop extensions for different VCS, that way even if someone wanted to use gitea with e.g. CVS they could.

@clarfonthey commented on GitHub (Jun 30, 2020): I also want to voice support for allowing multiple VCS types. Honestly, there are still lots of systems out there that use VCS other than git and allowing users to mirror those repos without converting them to git would be great. IMHO, the best thing would be to abstract the git logic so that ultimately people could develop extensions for different VCS, that way even if someone wanted to use gitea with e.g. CVS they could.

GiteaMirror commented

@VickyRampin commented on GitHub (Jun 30, 2020):

Also wanted to chime in with my support for multiple VCS types. The Hg and SVN folks are kind of being left high and dry by other hosting platforms, and Gitea would have a great competitive advantage if it was to support multiple VCS's, especially with the ability to self-host (particularly important for my communities, in academia).

@VickyRampin commented on GitHub (Jun 30, 2020): Also wanted to chime in with my support for multiple VCS types. The Hg and SVN folks are kind of being left high and dry by other hosting platforms, and Gitea would have a great competitive advantage if it was to support multiple VCS's, especially with the ability to self-host (particularly important for my communities, in academia).

GiteaMirror commented

@zeripath commented on GitHub (Jun 30, 2020):

git-as-svn should still work with Gitea.

@zeripath commented on GitHub (Jun 30, 2020): git-as-svn should still work with Gitea.

GiteaMirror commented

@clarfonthey commented on GitHub (Jun 30, 2020):

As I said, converting to git isn't really support, it's a workaround. The conversion isn't lossless, and it doesn't enable bidirectional operation, just unidirectional.

@clarfonthey commented on GitHub (Jun 30, 2020): As I said, converting to git isn't really support, it's a workaround. The conversion isn't lossless, and it doesn't enable bidirectional operation, just unidirectional.

GiteaMirror commented

https://github.com/bozaro/git-as-svn

@zeripath commented on GitHub (Jul 1, 2020):

@clarfon I meant:

Which does allow bidrectional operation.

@zeripath commented on GitHub (Jul 1, 2020): @clarfon I meant: https://github.com/bozaro/git-as-svn Which does allow bidrectional operation.

GiteaMirror commented

@Qix- commented on GitHub (Nov 11, 2020):

If for nothing else, being able to mirror murcurial repositories would be highly beneficial, even if they are "read only" from a git standpoint.

@Qix- commented on GitHub (Nov 11, 2020): If for nothing else, being able to mirror murcurial repositories would be highly beneficial, even if they are "read only" from a git standpoint.

GiteaMirror commented

@techknowlogick commented on GitHub (Dec 9, 2020):

Closing this as we are volunteers and we likely don't currently have the resources to do this. A lot of our code assumes git as VCS, and would take a large amount of effort to add another one. This isn't to say we wouldn't add HG support, but it would need someone to sponsor development and reviewers as large PRs (which this would need), take a lot of effort not just to make but review as well. It would also need coordination with maintainers so that perhaps PRs are split up into multiple PRs instead of just one big one, and to discuss approach prior to getting started.

@techknowlogick commented on GitHub (Dec 9, 2020): Closing this as we are volunteers and we likely don't currently have the resources to do this. A lot of our code assumes git as VCS, and would take a large amount of effort to add another one. This isn't to say we wouldn't add HG support, but it would need someone to sponsor development and reviewers as large PRs (which this would need), take a lot of effort not just to make but review as well. It would also need coordination with maintainers so that perhaps PRs are split up into multiple PRs instead of just one big one, and to discuss approach prior to getting started.

GiteaMirror commented