From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Daniel Jacques <dnj@google.com>
Subject: Re: What's cooking in git.git (Mar 2018, #06; Fri, 30)
Date: Wed, 4 Apr 2018 16:49:21 -0400 [thread overview]
Message-ID: <20180404204920.GA15402@sigill.intra.peff.net> (raw)
In-Reply-To: <87a7uow0jc.fsf@evledraar.gmail.com>
On Sat, Mar 31, 2018 at 08:41:11PM +0200, Ævar Arnfjörð Bjarmason wrote:
> > [...]
> > * jk/drop-ancient-curl (2017-08-09) 5 commits
> > - http: #error on too-old curl
> > - curl: remove ifdef'd code never used with curl >=7.19.4
> > - http: drop support for curl < 7.19.4
> > - http: drop support for curl < 7.16.0
> > - http: drop support for curl < 7.11.1
> >
> > Some code in http.c that has bitrot is being removed.
> >
> > Expecting a reroll.
>
> This has been idle for a long time. Peff: What's left to be done for it?
It wasn't clear to me we actually wanted to do this. It got some
complaints, and then somebody showed up to actually fix the compilation
problems with the old versions.
It also isn't that much of a burden to carry the #ifdefs. The main
question is whether we're doing a disservice to users, since those old
setups likely aren't well tested.
Even if we do proceed, I'm not sure if we'd want the top #error patch,
given the reports that distros will sometimes backport features.
-Peff
next prev parent reply other threads:[~2018-04-04 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 20:38 What's cooking in git.git (Mar 2018, #06; Fri, 30) Junio C Hamano
2018-03-30 20:59 ` Thomas Gummerer
2018-03-30 21:38 ` Junio C Hamano
2018-03-30 21:51 ` Jeff Hostetler
2018-03-31 9:39 ` Duy Nguyen
2018-03-31 18:41 ` Ævar Arnfjörð Bjarmason
2018-04-04 20:49 ` Jeff King [this message]
2018-04-03 13:12 ` js/runtime-prefix-windows, was " Johannes Schindelin
2018-04-04 17:31 ` Johannes Sixt
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=20180404204920.GA15402@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=dnj@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).