[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7
From: |
Ralph Corderoy |
Subject: |
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7 |
Date: |
Mon, 27 Nov 2017 15:39:54 +0000 |
Hi David,
> It looks like Ralph found and fixed all hard-coded uses of the ','
> backup prefix, including the three in test-mhfixmsg.
I also ./configured with --with-hash-backup to make sure, and have that
as my default for development now. I did notice that the distcheck
target fails to pass that on, along with quite a few other user-chosen
options? Is that deliberate? I see there's
AM_DISTCHECK_CONFIGURE_FLAGS, presumably that's where they'd go.
It has the convenient side-effect at the moment of using `#' for the top
build, and `,' for the distcheck, but we'd ideally stress a buildbot by
trying quite a few configure combinations, including throwing in a
symlink. Speaking of which, is there someone on the list familiar with
buildbot that would want to host a public one for nmh?
> > (Yes, this is intended to imply that your suggested fix of pwd -P
> > worked perfectly.):
>
> If Ralph is unavailable to commit the fix soon, I will.
It's 0e593b90 on master.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7, Steven Winikoff, 2017/11/26
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7, David Levine, 2017/11/26
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7, Ken Hornstein, 2017/11/26
Re: [Nmh-workers] possible problem with mhfixmsg in nmh-1.7, Steven Winikoff, 2017/11/26