git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	"Randall S. Becker" <the.n.e.key@gmail.com>,
	git@vger.kernel.org,
	"Randall S. Becker" <randall.becker@nexbridge.ca>,
	"Randall S . Becker" <rsbecker@nexbridge.com>
Subject: Re: [PATCH v2 1/2] Teach git version --build-options about libcurl
Date: Thu, 25 Jul 2024 20:41:27 -0400	[thread overview]
Message-ID: <20240726004127.GA611651@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq7cd9lccl.fsf@gitster.g>

On Thu, Jul 25, 2024 at 08:28:58AM -0700, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> >> A command with a name along the lines of `git diagnose`, I'd say.
> >
> > OK. I don't really care much either way how it is spelled, though my
> > inclination is that we already have a confusing number of commands and
> > should avoid adding more.
> 
> I think what you are responding to is an oblique reference to a
> command that already exists, and there is no need to worry about
> adding more ;-).  If "bugreport" is not farming out the task of
> collecting the information to it, "bugreport" need to be corrected
> to do so (while "diagnose" may have to learn to collect more, if
> "bugreport" collects things that "diagnose" does not (yet)).

Oh, sorry, I somehow missed when diagnose was added. Yeah, that seems
like a perfectly reasonable place to put it, though like bugreport it
has the same annoyance that I just want to dump the info to stdout, not
make a zipfile.

Curiously, it seems to segfault for me when run outside a repository. :-/
The issue is a NULL the_repository->objects->odb pointer passed into
dir_file_stats(). But obviously that bug is orthogonal to the discussion
here.

-Peff

  reply	other threads:[~2024-07-26  0:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 18:09 [PATCH v2 0/2] Teach git version --build-options about zlib+libcurl Randall S. Becker
2024-06-21 18:09 ` [PATCH v2 1/2] Teach git version --build-options about libcurl Randall S. Becker
2024-06-24 14:13   ` Johannes Schindelin
2024-06-24 14:33     ` Randall Becker
2024-06-24 17:08       ` Dragan Simic
2024-06-24 21:15         ` rsbecker
2024-06-24 21:52           ` Dragan Simic
2024-06-24 21:56             ` Randall Becker
2024-07-24 10:51       ` Johannes Schindelin
2024-06-24 15:29     ` Jeff King
2024-06-24 16:06     ` Junio C Hamano
2024-06-24 23:55       ` Jeff King
2024-06-25  0:00         ` Junio C Hamano
2024-07-24 10:48         ` Johannes Schindelin
2024-07-24 20:55           ` Jeff King
2024-07-24 22:17             ` Johannes Schindelin
2024-07-25  6:52               ` Jeff King
2024-07-25 15:28                 ` Junio C Hamano
2024-07-26  0:41                   ` Jeff King [this message]
2024-06-21 18:09 ` [PATCH v2 2/2] Teach git version --build-options about zlib versions Randall S. Becker
2024-06-24 14:15   ` Johannes Schindelin
2024-06-24 14:38     ` Randall Becker
2024-07-24 11:02       ` Johannes Schindelin
2024-07-24 13:36         ` Randall Becker
2024-07-24 16:21           ` Junio C Hamano
2024-07-24 16:33             ` rsbecker

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240726004127.GA611651@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=randall.becker@nexbridge.ca \
    --cc=rsbecker@nexbridge.com \
    --cc=the.n.e.key@gmail.com \
    /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.
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 NNTP newsgroup(s).