From: David Bremner <david@tethera.net>
To: Vladimir.Marek@oracle.com, notmuch@notmuchmail.org
Cc: Vladimir Marek <vlmarek@volny.cz>
Subject: Re: [PATCH 1/4] Make configure use /bin/bash instead of /bin/sh
Date: Mon, 30 Apr 2012 08:58:18 -0300 [thread overview]
Message-ID: <87haw1ph2d.fsf@zancas.localnet> (raw)
In-Reply-To: <1333966665-10469-2-git-send-email-Vladimir.Marek@oracle.com>
Vladimir.Marek@oracle.com writes:
> diff --git a/configure b/configure
> index 71981b7..6870341 100755
> --- a/configure
> +++ b/configure
> @@ -1,4 +1,4 @@
> -#! /bin/sh
> +#! /bin/bash
I realize the true story is more complicated than this, but how do
people feel about specifying bash for configure until/unless we get a
nicer solution?
d
next prev parent reply other threads:[~2012-04-30 11:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 10:17 notmuch on Solaris Vladimir.Marek
2012-04-09 10:17 ` [PATCH 1/4] Make configure use /bin/bash instead of /bin/sh Vladimir.Marek
2012-04-09 11:10 ` Jani Nikula
2012-04-09 12:19 ` Vladimir Marek
2012-04-10 17:26 ` Tomi Ollila
2012-04-11 8:43 ` Vladimir Marek
2012-04-11 18:47 ` Tomi Ollila
2012-04-30 11:58 ` David Bremner [this message]
2012-04-30 12:09 ` Tomi Ollila
2012-04-09 10:17 ` [PATCH 2/4] dirent->d_type not available on Soalris Vladimir.Marek
2012-04-09 11:17 ` Jani Nikula
2012-04-09 15:12 ` Vladimir Marek
2012-04-09 15:46 ` Adam Wolfe Gordon
2012-04-09 16:32 ` Vladimir.Marek
2012-04-11 18:57 ` Tomi Ollila
2012-04-11 19:36 ` Austin Clements
2012-04-09 10:17 ` [PATCH 3/4] Private strsep implementation Vladimir.Marek
2012-10-15 5:05 ` Ethan Glasser-Camp
2012-04-09 10:17 ` [PATCH 4/4] Explicitly type void* pointers Vladimir.Marek
2012-04-09 11:04 ` Jani Nikula
2012-04-09 18:15 ` Vladimir Marek
2012-04-09 21:31 ` Jani Nikula
2012-04-10 6:53 ` Vladimir Marek
2012-04-11 21:11 ` Austin Clements
2012-04-12 8:02 ` Jani Nikula
2012-04-12 17:57 ` Austin Clements
2012-04-15 21:05 ` Jani Nikula
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87haw1ph2d.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=Vladimir.Marek@oracle.com \
--cc=notmuch@notmuchmail.org \
--cc=vlmarek@volny.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).