Re: [PATCH] contrib: drop hg-to-git script

From: Jeff King <peff@peff.net>
Date: Mar 22, 2024, 23:43 UTC
Message-ID: <20240322234354.GC2049941@coredump.intra.peff.net>
In-Reply-To: <xmqqjzlu2r8n.fsf@gitster.g>

On Fri, Mar 22, 2024 at 08:58:16AM -0700, Junio C Hamano wrote:

Show 5 quoted lines

> Those with specific needs (e.g., "A project uses Mercuial; I want
> its history in Git because I am used to it more") will never come to
> our contrib/ as their first place to look, but they may still find
> us in https://letmegooglethat.com/?q=mercurial+to+git if we left an
> otherwise empty directory there.

Thanks, I was going to write something similar, but you did it much better than I would have. :)

I was curious what results such a search _would_ turn up these days. The top hits for me (keeping in mind that sometimes search results are personalized, of course) are:

  - https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git

    which suggests hg-fast-export to git-fast-import for a one-time
    conversion.

  - https://docs.github.com/en/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository

    which does likewise.

  - https://www.alexpage.de/guides/convert-a-mercurial-hg-repository-to-git/

    which suggests using hg-git to push into the Git repository.

I suggested remote-hg or cinnabar, which is what I would have turned to. But I guess those are more about continuous interoperability rather than a one-shot conversion (and of course are based on fast-export/import under the hood anyway).

Anyway, the important takeaway to me is that searches are not likely to end up at contrib/hg-to-git, with people wondering where it went. They will point directly to the alternatives.

-Peff