From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: js/gcc-8-and-9, was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)
Date: Mon, 17 Jun 2019 12:54:43 -0700 [thread overview]
Message-ID: <xmqqpnncrnr0.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1906171940201.44@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 17 Jun 2019 19:41:21 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> On Fri, 14 Jun 2019, Junio C Hamano wrote:
>
>> * js/gcc-8-and-9 (2019-06-13) 4 commits
>> - config: avoid calling `labs()` on too-large data type
>> - winansi: simplify loading the GetCurrentConsoleFontEx() function
>> - kwset: allow building with GCC 8
>> - poll (mingw): allow compiling with GCC 8 and DEVELOPER=1
>>
>> Code clean-up for new compilers.
>>
>> The 'kwset' one may want to be discussed a bit longer. Perhaps
>> merge the other three earlier to 'next' and then to 'master'
>> separately?
>
> Or just take the kwset one with an adjusted commit message because it may
> turn out that the kwset update will be blocked for a while because of
> licensing issues?
Sorry, but I do not understand why you'd want to "take" one that you
suspect may be blocked for a while. I'd rather see us unblock the
other ones that are unproblematic, without taking them hostage,
which was what I meant.
next prev parent reply other threads:[~2019-06-17 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:50 What's cooking in git.git (Jun 2019, #04; Fri, 14) Junio C Hamano
2019-06-17 17:41 ` js/gcc-8-and-9, was " Johannes Schindelin
2019-06-17 19:54 ` Junio C Hamano [this message]
2019-06-18 10:26 ` Johannes Schindelin
2019-06-19 14:28 ` Junio C Hamano
2019-06-17 18:06 ` pw/rebase-abort-clean-rewritten, " Johannes Schindelin
2019-06-17 19:04 ` Phillip Wood
2019-06-18 3:30 ` Junio C Hamano
2019-06-20 9:34 ` Phillip Wood
2019-06-21 13:27 ` Johannes Schindelin
2019-06-17 18:25 ` sg/rebase-progress, " Johannes Schindelin
2019-06-18 13:36 ` ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)) Derrick Stolee
2019-06-19 14:32 ` Junio C Hamano
2019-06-19 14:37 ` Derrick Stolee
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=xmqqpnncrnr0.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).