From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>,
"'Stefan Beller'" <sbeller@google.com>
Cc: "'git'" <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.17.0
Date: Mon, 2 Apr 2018 19:47:10 -0400 [thread overview]
Message-ID: <01a501d3cadc$ee24a070$ca6de150$@nexbridge.com> (raw)
In-Reply-To: <xmqqfu4dxkky.fsf@gitster-ct.c.googlers.com>
On April 2, 2018 7:20 PM, Junio C Hamano wrote:
> To: Stefan Beller <sbeller@google.com>
> Cc: Randall S. Becker <rsbecker@nexbridge.com>; git <git@vger.kernel.org>
> Subject: Re: [ANNOUNCE] Git v2.17.0
>
> Stefan Beller <sbeller@google.com> writes:
>
> > Patch at
> > https://public-
> inbox.org/git/010f01d38a9e$a5c4f290$f14ed7b0$@nexbridge
> > .com/
>
> Thanks for a pointer. I think it was left behind and got forgotten while
> waiting for a reroll and tying the loose ends.
>
> I'll go offline for most of the rest of the week. It would be wonderful
if Git
> 2.17 turns out to be flawless, but that is not a realistic expectation.
Wishing
> for the second best, I'd very much appreciate it if people worked hard to
find
> and fix regressions and collect materials for its first maintenance
release
> 2.17.1 ;-)
No worries. We're running the test suite now (NonStop Platform) and assuming
all is good, it goes into our prod environment this week.
Cheers,
Randall
next prev parent reply other threads:[~2018-04-02 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 19:34 [ANNOUNCE] Git v2.17.0 Junio C Hamano
2018-04-02 19:57 ` Randall S. Becker
2018-04-02 20:01 ` Stefan Beller
2018-04-02 20:10 ` Randall S. Becker
2018-04-02 23:19 ` Junio C Hamano
2018-04-02 23:47 ` Randall S. Becker [this message]
2018-04-04 2:39 ` Randall S. Becker
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='01a501d3cadc$ee24a070$ca6de150$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).