From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, git-packagers@googlegroups.com,
git-for-windows@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.16.0-rc1
Date: Sat, 6 Jan 2018 13:59:55 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1801061354430.1337@wbunaarf-fpuvaqryva.tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqbmi7ano1.fsf@gitster.mtv.corp.google.com>
Hi team,
On Fri, 5 Jan 2018, Junio C Hamano wrote:
> A release candidate Git v2.16.0-rc1 is now available for testing
> at the usual places. It is comprised of 455 non-merge commits
> since v2.15.0, contributed by 79 people, 23 of which are new faces.
I rebased Git for Windows' thicket of patch series on top, and I already
got this when running t0021:
# failed 10 among 26 test(s)
1..26
It also seems that the v2.16.0-rc1 *without* Git for Windows' patches on
top displays the very same problem: the test suite does *not* pass on
Windows.
As it is, I am not willing to wreck my weekend, so this will have to wait
until Monday (and Git for Windows v2.16.0-rc1 with it).
Ciao,
Johannes
next prev parent reply other threads:[~2018-01-06 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 23:30 [ANNOUNCE] Git v2.16.0-rc1 Junio C Hamano
2018-01-06 12:59 ` Johannes Schindelin [this message]
2018-01-06 22:01 ` Johannes Schindelin
2018-01-09 21:42 ` Junio C Hamano
2018-01-09 23:55 ` Junio C Hamano
2018-01-10 17:40 ` Johannes Schindelin
2018-01-10 20:09 ` Junio C Hamano
2018-01-10 17:37 ` Johannes Schindelin
2018-01-10 17:54 ` [git-for-windows] " 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=nycvar.QRO.7.76.6.1801061354430.1337@wbunaarf-fpuvaqryva.tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git-packagers@googlegroups.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).