All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] update configure.ac to autoconf 2.61
Date: Wed, 03 Sep 2008 19:43:22 -0400	[thread overview]
Message-ID: <1220485402.5868.8.camel@dv> (raw)
In-Reply-To: <1220448464.4164.53.camel@fz.local>

On Wed, 2008-09-03 at 15:27 +0200, Felix Zielcke wrote:
> Attached patch is generated via `autoupdate --force' from autoconf 2.61
> a svn-diff after ./autogen.sh doestn't show anything more, because
> the ./configure script in SVN is already generated with autoconf 2.61.
> 
> autoconf 2.61 is dated 17.11.2006 on ftp.gnu.org
> 
> Debian etch + lenny have autoconf 2.61
> etch has been released 8th April 2007
> Ubuntu has it since feisty which has been released 19th April 2007
> 
> I haven't checked the others but I think this is recent enough for the
> configure.ac (remember it's generated by ./autogen.sh anyway)
> 
> Yes I really want to get rid of old stuff and if you even only need to
> call `autoupdate --force' ;)

I don't see any old stuff being removed.  I don't see any justification
for any of the changes.  The new code is longer and less readable.  I
don't think AC_TRY_COMPILE is a big problem yet.  It's not like it won't
produce a valid test.

In any case, please try to avoid extra long lines where it can be easily
avoided.

Okuji wrote that he uses Autoconf 2.59, so it would be nice to check
that your changes would still work with that version.

-- 
Regards,
Pavel Roskin



  parent reply	other threads:[~2008-09-03 23:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 13:27 [PATCH] update configure.ac to autoconf 2.61 Felix Zielcke
2008-09-03 14:51 ` Felix Zielcke
2008-09-03 23:47   ` Pavel Roskin
2008-09-04  7:55     ` Felix Zielcke
2008-09-03 23:43 ` Pavel Roskin [this message]
2008-09-04  7:45   ` Felix Zielcke
2008-09-04 16:49     ` Pavel Roskin
2008-09-04 17:32       ` Felix Zielcke
2008-09-21 17:39     ` Felix Zielcke

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=1220485402.5868.8.camel@dv \
    --to=proski@gnu.org \
    --cc=grub-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.
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.