From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Eric Sunshine'" <sunshine@sunshineco.us>
Cc: "'Git List'" <git@vger.kernel.org>
Subject: RE: [PATCH v3 2/4] config.mak.uname: support for modern HPE NonStop config.
Date: Fri, 28 Dec 2018 15:03:36 -0500 [thread overview]
Message-ID: <000c01d49ee8$6ea2a0a0$4be7e1e0$@nexbridge.com> (raw)
In-Reply-To: <CAPig+cTjn4je8dOANs-xHhU_NYRw-Twm22HSnSLNXTkDB-qRYw@mail.gmail.com>
On December 28, 2018 14:43, Eric Sunshine wrote:
> On Thu, Dec 27, 2018 at 5:39 PM <randall.s.becker@rogers.com> wrote:
> > A number of configuration options are not automatically detected by
> > configure mechanisms, including the location of Perl and Python.
> >
> > There was a problem at a specific set of operating system versions
> > that caused getopt to have compile errors. Account for this by
> > providing emulation defines for those versions.
>
> This version of the patch looks much better and addresses my comments on
> previous attempts. One note below...
>
> > Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
> > ---
> > diff --git a/config.mak.uname b/config.mak.uname @@ -441,26 +441,45
> @@
> > ifeq ($(uname_S),NONSTOP_KERNEL)
> > + # The current /usr/coreutils/rm at lowest support level does not work
> > + # with the git test structure. Long paths cause nftw as in
> > + # 'trash directory...' cause rm to terminate prematurely without fully
> > + # removing the directory at OS releases J06.21 and L17.02.
> > + # Default to the older rm until those two releases are deprecated.
> > + RM = /bin/rm -f
>
> Thanks, this comment does a much better job of explaining the actual
> problem and selling the solution.
>
> There is a slight grammatical problem:
>
> Long paths _cause_ ... _cause_ rm to terminate...
>
> which might deserve fixing.
Rerolled. Thanks.
prev parent reply other threads:[~2018-12-28 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 22:38 [PATCH v3 2/4] config.mak.uname: support for modern HPE NonStop config randall.s.becker
2018-12-28 19:42 ` Eric Sunshine
2018-12-28 20:03 ` Randall S. Becker [this message]
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='000c01d49ee8$6ea2a0a0$4be7e1e0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.us \
/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).