git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	 Eric Sunshine <sunshine@sunshineco.com>,
	 Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 Ben Knoble <ben.knoble@gmail.com>,
	brian m carlson <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] imap-send: add option to mark sent messages as read or unread
Date: Wed, 23 Jul 2025 10:46:03 -0700	[thread overview]
Message-ID: <xmqq7bzyol5w.fsf@gitster.g> (raw)
In-Reply-To: <PN0PR01MB95888028E0BD985DA07B9C60B85FA@PN0PR01MB9588.INDPRD01.PROD.OUTLOOK.COM> (Aditya Garg's message of "Wed, 23 Jul 2025 15:45:25 +0000")

Aditya Garg <gargaditya08@live.com> writes:

> The GitHub actions workflows are failing because CURLOPT_UPLOAD_FLAGS were introduced in v8.13.0 of libcurl, which is just 3 months old, and the CI has an older version.
>
> Not sure if version checks are needed here or not.

Hold onto the patch, without sending it to me or to the list, until
we raise the requirement for libcURL again perhaps in a few years,
at which time we may consider adpoting this feature.

I do not think we want more conditional compilation.

Thanks.

  reply	other threads:[~2025-07-23 17:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 15:45 [PATCH] imap-send: add option to mark sent messages as read or unread Aditya Garg
2025-07-23 17:46 ` Junio C Hamano [this message]
2025-07-23 17:49   ` Aditya Garg
  -- strict thread matches above, loose matches on Subject: below --
2025-07-23 17:55 Aditya Garg
2025-07-23 12:29 Aditya Garg
2025-07-23 17:25 ` Junio C Hamano
2025-07-23 17:33   ` Aditya Garg
2025-07-23 17:35     ` Aditya Garg
2025-07-23 17:56       ` Junio C Hamano
2025-07-23 18:00         ` Aditya Garg
2025-07-23 17:55     ` Junio C Hamano
2025-07-23 17:52   ` 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

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

  git send-email \
    --in-reply-to=xmqq7bzyol5w.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=gargaditya08@live.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=sunshine@sunshineco.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).