git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jeff King" <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: move some test-tools to 'unstable plumbing' built-ins
Date: Mon, 08 Nov 2021 11:16:29 -0800	[thread overview]
Message-ID: <xmqq7ddiv4oi.fsf@gitster.g> (raw)
In-Reply-To: <YYgHhaOAsv7pVAMi@nand.local> (Taylor Blau's message of "Sun, 7 Nov 2021 12:06:13 -0500")

Taylor Blau <me@ttaylorr.com> writes:

> In my experience I *rarely* rely on test-helpers when debugging wedged
> repositories, and much more often end up either in gdb, or in an
> anonymized copy of the repository on a different server. I would imagine
> that others have similar experiences.
>
> So unless we had a much more compelling reason to have the test helpers
> more readily available, I do not think that the risk our users will
> begin to depend on these unstable tools is worth taking.

OK.  It sounds like a sensible argument against such a change.

Thanks.

  reply	other threads:[~2021-11-08 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  9:01 [PATCH] test_bitmap_hashes(): handle repository without bitmaps Jeff King
2021-11-05 18:52 ` Junio C Hamano
2021-11-05 19:11   ` Taylor Blau
2021-11-05 23:29     ` Jeff King
2021-11-06  4:08     ` move some test-tools to 'unstable plumbing' built-ins (was: [PATCH] test_bitmap_hashes(): handle repository without bitmaps) Ævar Arnfjörð Bjarmason
2021-11-07 17:06       ` Taylor Blau
2021-11-08 19:16         ` Junio C Hamano [this message]
2021-11-08 20:19           ` move some test-tools to 'unstable plumbing' built-ins Ævar Arnfjörð Bjarmason
2021-11-08 22:06             ` Taylor Blau

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=xmqq7ddiv4oi.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.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).