Re: migrate repository from mercurial to git
On 12/10/21 18:14, Uwe Brauer wrote: On 12/10/21 12:29, Łukasz Michalski wrote: Hi, I would like to migrate a repository myrepo from mercurial to git. I want to rename mercurial repository to myrepo_old and use orginal name for new git repository. Is it enough to rename mercurial repository on disk and copy new one under original name? Old one can have some closed pull requests. Yes, that should work and be safe, especially if you do the renaming and repo creation in Kallithea. The new repo will be "different" from the old one, even if the name is reused. Access rules and PRs etc will be different. I am deeply confused. Are you saying kallithea can convert a mercurial repository to git without any further set up? No, that's not what I'm saying. Kallithea does not have conversion built in. I do not see Łukasz asking about the actual conversion process. I'm sure he is aware of the options and trade-offs and can make the conversion manually. He is only asking about how he can put a new Git repo in the place where the Mercurial repo used to live. It could be very interesting to develop a hosting solution that was completely VCS agnostic. Where the immutable main branches of each "repository" were exposed in "all" kinds of VCSs, so users and contributors could work and submit changes in any way they want. But I doubt anybody wants to invest enough to make that happen ;-) It would be more simple to integrate external conversion tools so a click off a button in Kallithea would make a one-shot conversion to another repo format with some chosen handling of the fundamental VCS differences. /Mads ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
Re: migrate repository from mercurial to git
>>> "MK" == Mads Kiilerich writes: > On 12/10/21 12:29, Łukasz Michalski wrote: >> Hi, >> >> I would like to migrate a repository myrepo from mercurial to git. >> >> I want to rename mercurial repository to myrepo_old and use orginal name for >> new git repository. >> >> Is it enough to rename mercurial repository on disk and copy new one under >> original name? Old one can have some closed pull requests. > Yes, that should work and be safe, especially if you do the renaming > and repo creation in Kallithea. The new repo will be "different" from > the old one, even if the name is reused. Access rules and PRs etc will > be different. I am deeply confused. Are you saying kallithea can convert a mercurial repository to git without any further set up? How are named branches be converted? How are bookmarks and topics? smime.p7s Description: S/MIME cryptographic signature ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
Re: migrate repository from mercurial to git
On 12/10/21 12:29, Łukasz Michalski wrote: Hi, I would like to migrate a repository myrepo from mercurial to git. I want to rename mercurial repository to myrepo_old and use orginal name for new git repository. Is it enough to rename mercurial repository on disk and copy new one under original name? Old one can have some closed pull requests. Yes, that should work and be safe, especially if you do the renaming and repo creation in Kallithea. The new repo will be "different" from the old one, even if the name is reused. Access rules and PRs etc will be different. Internally, Kallithea is using numerical primary key IDs to store database data. The (current) repository name is only used to look up the ID when a user is accessing web interface or with protocol access, and again when finding the repository on disk. Only the access log will not only use the ID but laso duplicate the (current) repository name so the logs are useful, even if the repo is removed completely. /Mads ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
Re: migrate repository from mercurial to git
>>> "ŁM" == Łukasz Michalski writes: > Hi, > I would like to migrate a repository myrepo from mercurial to git. As a die hard fan of mercurial I find this sad, you will not be able to use named branches and topics, and local revision numbers (for convenience) anymore. > I want to rename mercurial repository to myrepo_old and use orginal name for > new git repository. I have done similar things, and the best strategy is: generate an empty git repository. Use the hg-git pluging and push to that repository. One question: did you use named branches???. If you did you would need a specific change set of hg-git this exporting named branches is still not in the stable release. smime.p7s Description: S/MIME cryptographic signature ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
migrate repository from mercurial to git
Hi, I would like to migrate a repository myrepo from mercurial to git. I want to rename mercurial repository to myrepo_old and use orginal name for new git repository. Is it enough to rename mercurial repository on disk and copy new one under original name? Old one can have some closed pull requests. Thanks, Łukasz ___ kallithea-general mailing list kallithea-general@sfconservancy.org https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
