From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Matthew Rollings <admin@stealthcopter.com>,
Stelian Pop <stelian@popies.net>,
git@vger.kernel.org
Subject: Re: [PATCH] contrib: drop hg-to-git script
Date: Fri, 22 Mar 2024 19:43:54 -0400 [thread overview]
Message-ID: <20240322234354.GC2049941@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqjzlu2r8n.fsf@gitster.g>
On Fri, Mar 22, 2024 at 08:58:16AM -0700, Junio C Hamano wrote:
> 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
next prev parent reply other threads:[~2024-03-22 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 9:48 [PATCH] contrib: drop hg-to-git script Jeff King
2024-03-20 14:39 ` Junio C Hamano
2024-03-22 7:31 ` Johannes Schindelin
2024-03-22 8:36 ` Stelian Pop
2024-03-22 16:48 ` Junio C Hamano
2024-03-22 15:58 ` Junio C Hamano
2024-03-22 23:43 ` Jeff King [this message]
2024-03-23 18:49 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240322234354.GC2049941@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=admin@stealthcopter.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stelian@popies.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).