From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: randall.s.becker@rogers.com, git <git@vger.kernel.org>,
"Randall S. Becker" <rsbecker@nexbridge.com>
Subject: Re: [RFC PATCH] NonStop port changes for git 2.16.0.
Date: Fri, 19 Jan 2018 01:10:40 +0100 [thread overview]
Message-ID: <87a7xaiu7z.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CAGZ79kb4Zr6QnNydRX56B_4Jo5fveufBFJAD7r_8U-NRSMa2qQ@mail.gmail.com>
On Thu, Jan 18 2018, Stefan Beller jotted:
> On Thu, Jan 18, 2018 at 2:42 PM, <randall.s.becker@rogers.com> wrote:
>> Further: there are 6 known breakages that have been reported. The perl
>> issues relating to completion codes are being examined at present by the
>> platform support teams so are not addressed by this patch.
>
> For perl I'd suggest cc'ing Ævar (cc'd just now) as that seems his
> field of expertise.
Just to make sure I'm keeping up, this refers to some breakage not
detailed in the patch above, right?
The only perl-related change I see is undoing part of 6c109904bc ("Port
to HP NonStop", 2012-09-19) having to do with how we find perl/python
(which, not being at all familiar with NonStop, makes sense to me).
But sure, if there's some details about those 6 issues I might have time
to take a look, but it sounds like it's being looked at by NonStop
support...
next prev parent reply other threads:[~2018-01-19 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 22:42 [RFC PATCH] NonStop port changes for git 2.16.0 randall.s.becker
2018-01-18 22:50 ` Stefan Beller
2018-01-19 0:10 ` Ævar Arnfjörð Bjarmason [this message]
2018-01-19 1:22 ` 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=87a7xaiu7z.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=randall.s.becker@rogers.com \
--cc=rsbecker@nexbridge.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.
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.