unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Subject: Re: configure{.in,} question
Date: Mon, 25 Oct 2010 22:08:44 +0200	[thread overview]
Message-ID: <m3bp6iqblf.fsf@quimbies.gnus.org> (raw)
In-Reply-To: 87sjzu2id5.fsf@lifelogs.com

Speaking of which, Andreas has just checked in configure made with
autoconf 2.68, so now there's a 4K line diff between anybody using 2.65
and what's in bzr.

If we're still going to have the configure file in bzr, would it be
possible to have the configure file be autogenerated on Savannah (or
somewhere), perhaps as a trigger after checking in configure.in?  That
way we won't get 4K line flapping between different autoconf versions,
at least.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




      reply	other threads:[~2010-10-25 20:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24 17:31 configure{.in,} question Lars Magne Ingebrigtsen
2010-10-24 19:38 ` Glenn Morris
2010-10-24 19:56   ` Lars Magne Ingebrigtsen
2010-10-24 20:07     ` Glenn Morris
2010-10-25  0:57       ` Stephen J. Turnbull
2010-10-25  8:38         ` Andreas Schwab
2010-10-25 14:43           ` Stephen J. Turnbull
2010-10-25 14:58             ` Andreas Schwab
2010-10-25 15:41               ` Stephen J. Turnbull
2010-10-25  8:47       ` Julien Danjou
2010-10-25  9:00         ` Andreas Schwab
2010-10-25  9:15         ` Eli Zaretskii
2010-10-25 16:06           ` Stefan Monnier
2010-10-25 18:04             ` Eli Zaretskii
2010-10-25 18:37               ` Glenn Morris
2010-10-25 19:59                 ` Stefan Monnier
2010-10-25 19:34               ` Stefan Monnier
2010-10-25 16:43           ` Glenn Morris
2010-10-25 19:11 ` Ted Zlatanov
2010-10-25 19:13   ` Lars Magne Ingebrigtsen
2010-10-25 19:16     ` Ted Zlatanov
2010-10-25 20:08       ` Lars Magne Ingebrigtsen [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3bp6iqblf.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).