On 2018-04-16 07:53:56 -0500, Paul Keusemann wrote:
> I have just built mutt-1.9.5 on several platforms and ran into a problem
> with the version.sh script on systems where /bin/sh is not bash.
I suppose you meant... where /bin/sh is not a POSIX shell.
On 2018-04-16 09:26:51 -0700, Kevin J. McCar
At 15:27 +0200 17 Apr 2018, Vincent Lefevre wrote:
I suppose that -r should work since .git must be readable to be
useful.
That's not actually true. When it's a directory, a large number of
operations can be done without it being readable (in my testing I
haven't come across anything that fa
With 1.9.5 out, I'd like to start moving towards a 1.10.0 release. This
cycle, I've had less time than usual, and have been more involved in the
git, gitlab, mailing list, trac tickets, and website migration (phew!).
So I don't know that there are a lot of huge new features.
However, several peop
On Mon, Apr 16, 2018 at 09:26:51AM -0700, Kevin J. McCarthy wrote:
> On Mon, Apr 16, 2018 at 10:18:57AM -0400, Aaron Schrab wrote:
> > At 15:41 +0200 16 Apr 2018, Gero Treuner wrote:
> > > On Mon, Apr 16, 2018 at 07:53:56AM -0500, Paul Keusemann wrote:
> > > > { [ -e ".git" ] && command -v git >/d
On Tue, Apr 17, 2018 at 02:28:17PM -0500, Derek Martin wrote:
> I believe Bourne shell allows compound tests like the following:
>
> [ -f $file -o -d $file ]
[Although, FWIW, I could have sworn Bourne shell supported -e as
well...]
--
Derek D. Martinhttp://www.pizzashack.org/ GPG Key I
On Tue, Apr 17, 2018 at 02:28:17PM -0500, Derek Martin wrote:
> Wasn't there some recent-ish notion that Mutt would now require
> vaguely modern (i.e. C99-compliant) systems to compile? If so,
> doesn't that implicitly include having a /bin/sh that is POSIX?
Yes, I (we) have been trying to move i
