git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>
Cc: "'Max Kirillov'" <max@max630.net>,
	"'SZEDER Gábor'" <szeder.dev@gmail.com>,
	git@vger.kernel.org, "Randall S. Becker" <rsbecker@nexbridge.com>
Subject: Re: [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) - Good News
Date: Mon, 18 Feb 2019 10:45:34 -0800	[thread overview]
Message-ID: <xmqqef852awh.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqq5ztj4l3j.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Sat, 16 Feb 2019 10:57:52 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> I have been wondering about the whole /dev/zero business.  Although
> we have b46221ff ("Merge branch 'rb/no-dev-zero-in-test'",
> 2019-02-13) in 'master', "git grep /dev/zero t" has hits in
> t/helper/test-sha1.sh and t/t4152-am-resume-override-opts.sh, so it
> must have been somewhat incomplete to help platforms that lack
> /dev/zero in the first place.
>
> We haven't heard from Dscho in European timezone, but I'm
> inclined to
>
>  - keep b46221ff in 'master', not reverted.
>  - apply Max's "t5562: do not reuse output files"
>
> to 'master' and hope that we can declare victory in this part of the
> code ;-).  There may be fix-ups for other topics before -rc2 on top
> of that, though.

Just to make sure you didn't miss the exchange, the above plan is
still the latest ("Max's patch is [1]).  As I'll be offline most of
the day today, you still have time to stop or make me change course
to avoid disaster by interjecting (which would be very much
appreciated).

Thanks.


[Reference]

*1* https://public-inbox.org/git/20181124093719.10705-1-max@max630.net/

  reply	other threads:[~2019-02-18 18:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 16:51 [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) - Good News Randall S. Becker
2019-02-16 17:02 ` Randall S. Becker
2019-02-16 18:05 ` Junio C Hamano
2019-02-16 18:24   ` Randall S. Becker
2019-02-16 18:57     ` Junio C Hamano
2019-02-18 18:45       ` Junio C Hamano [this message]
2019-02-18 18:50         ` Randall S. Becker
2019-02-19 10:05           ` Johannes Schindelin
2019-02-18 19:37       ` Johannes Schindelin
2019-02-18 21:57         ` Johannes Schindelin
2019-02-19 20:15           ` Max Kirillov
2019-02-19 20:36             ` Max Kirillov
2019-02-19 20:53             ` Randall S. Becker
2019-02-20 20:15             ` Johannes Schindelin
2019-02-18 20:24       ` Max Kirillov
2019-02-18 20:31         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqef852awh.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=max@max630.net \
    --cc=rsbecker@nexbridge.com \
    --cc=szeder.dev@gmail.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.
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 NNTP newsgroup(s).