all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Caldwell <david@porkrind.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 22556@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#22556: HEAD; autogen.sh automatic parameter isn't working
Date: Fri, 5 Feb 2016 10:06:56 -0800	[thread overview]
Message-ID: <56B4E4C0.8050701@porkrind.org> (raw)
In-Reply-To: <3h9hnt5qo.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

On 2/5/16 9:41 AM, Glenn Morris wrote:
> David Caldwell wrote:
> 
>>> The autoconf manual says that this is portable to all shells that
>>> support functions, so it should be fine, since autogen.sh uses
>>> functions.
>>
>> Sorry, were you referring to "${*-autoconf}" or "${*:-autoconf}" being
>> portable?
> 
> I meant that your patch should be fine to apply.
> But AFAICS at the next merge from emacs-25 the relevant code will all
> disappear anyway. Or there will be a merge conflict.

If the merge isn't going to happen today, would you mind installing the
patch (I would but I don't have a commit bit)? It's currently causing my
automated builds to break. And if I change the builder to pass the
"autoconf" flag, then if the code goes away in a merge it might break
again tomorrow.

> (BTW, please try to put the right version number in the subject.
> I thought this report was about the emacs-25 branch, but it seems it
> wasn't.)

Apologies, I even looked at it twice and thought it was correct. :-) I
guess I got confused because of the freeze and the recent version changes.

-David



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4239 bytes --]

  reply	other threads:[~2016-02-05 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 18:18 bug#22556: 25.0.90; autogen.sh automatic parameter isn't working David Caldwell
2016-02-05  2:32 ` Glenn Morris
2016-02-05  3:06   ` David Caldwell
2016-02-05 17:41     ` Glenn Morris
2016-02-05 18:06       ` David Caldwell [this message]
2016-02-05 22:18       ` Paul Eggert

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=56B4E4C0.8050701@porkrind.org \
    --to=david@porkrind.org \
    --cc=22556@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=rgm@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.