git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #03; Mon, 8)
Date: Wed, 10 Sep 2025 14:42:26 -0700	[thread overview]
Message-ID: <xmqqv7lqougt.fsf@gitster.g> (raw)
In-Reply-To: <20250910155450.GA1135031@coredump.intra.peff.net> (Jeff King's message of "Wed, 10 Sep 2025 11:54:50 -0400")

Jeff King <peff@peff.net> writes:

> On Mon, Sep 08, 2025 at 06:37:49PM -0700, Junio C Hamano wrote:
>
>> * jk/curl-global-trace-components (2025-08-27) 1 commit
>>  - curl: add support for curl_global_trace() components
>> 
>>  Adjust to the way newer versions of cURL selectivel enables tracing
>>  options, so that our tests can continue to work.
>> 
>>  Will merge to 'next'?
>>  source: <20250827080702.GA3572995@coredump.intra.peff.net>
>
> It doesn't seem to have gotten a lot of interest. But we have to do
> _something_ if we want tests to keep passing with the new version of
> curl. The other obvious alternatives is to try to modify the tests so
> that we don't have to modify the code to support the extra debugging
> knob. But I suspect that debugging knob may come in handy at some point
> in the future, and is worth having.
>
> -Peff

Thanks for pinging.  I was hoping that other people, not you, to say
the above, but perhaps our developer population is too small for
that?

Let's merge it to 'next'.

      reply	other threads:[~2025-09-10 21:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  1:37 What's cooking in git.git (Sep 2025, #03; Mon, 8) Junio C Hamano
2025-09-09  6:58 ` Elijah Newren
2025-09-09 19:35   ` Derrick Stolee
2025-09-09 21:20     ` Junio C Hamano
2025-09-10  7:42 ` Kristoffer Haugsbakk
2025-09-10 21:37   ` Junio C Hamano
2025-09-10 21:44     ` Kristoffer Haugsbakk
2025-09-10 15:32 ` Phillip Wood
2025-09-10 21:38   ` Junio C Hamano
2025-09-10 15:54 ` Jeff King
2025-09-10 21:42   ` 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

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

  git send-email \
    --in-reply-to=xmqqv7lqougt.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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.
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).