git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
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: Sat, 23 Mar 2024 11:49:29 -0700	[thread overview]
Message-ID: <xmqqh6gwwzpi.fsf@gitster.g> (raw)
In-Reply-To: <20240322234354.GC2049941@coredump.intra.peff.net> (Jeff King's message of "Fri, 22 Mar 2024 19:43:54 -0400")

Jeff King <peff@peff.net> writes:

> 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.

And what is most attractive is that the list of alternatives they
will see in there searches will be updated as new and better ones
appear, unlike contrib/hg-to-git/README that we would need to
conciously maintain, which we are unlikely to do.

We might want to see if there are other contrib/ ones with only
tombstone READMEs and remove them as a part of spring (in the
northern hemisphere) cleaning, #leftoverbits, citing what we
discussed in this thread as the rationale.

Thanks.


      reply	other threads:[~2024-03-23 18:49 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
2024-03-23 18:49       ` Junio C Hamano [this message]

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=xmqqh6gwwzpi.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=admin@stealthcopter.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --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).