From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Daniel Jacques <dnj@google.com>
Subject: Re: What's cooking in git.git (Mar 2018, #06; Fri, 30)
Date: Sat, 31 Mar 2018 20:41:11 +0200 [thread overview]
Message-ID: <87a7uow0jc.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqvadd1epf.fsf@gitster-ct.c.googlers.com>
On Fri, Mar 30 2018, Junio C. Hamano 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?
> [...]
> * dj/runtime-prefix (2018-03-25) 3 commits
> - exec_cmd: RUNTIME_PREFIX on some POSIX systems
> - Makefile: add Perl runtime prefix support
> - Makefile: generate Perl header from template file
> (this branch is used by js/runtime-prefix-windows.)
>
> A build-time option has been added to allow Git to be told to refer
> to its associated files relative to the main binary, in the same
> way that has been possible on Windows for quite some time, for
> Linux, BSDs and Darwin.
>
> Is this, together with the js/runtime-prefix-windows topic, ready
> for 'next'?
dj/runtime-prefix look good to me (and I've been the reviewing it the
most it seems), I don't see any problems with js/runtime-prefix-windows
from peeking at it, but I haven't run it for obvious reasons.
next prev parent reply other threads:[~2018-03-31 18:41 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 [this message]
2018-04-04 20:49 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7uow0jc.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=dnj@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.