From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH v2] sim: move from common.m4 to SIM_AC_COMMON
Date: Thu, 29 Sep 2011 02:01:00 -0000 [thread overview]
Message-ID: <201109282200.56083.vapier@gentoo.org> (raw)
In-Reply-To: <1310436112-8596-1-git-send-email-vapier@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 312 bytes --]
On Monday, July 11, 2011 22:01:52 Mike Frysinger wrote:
> Now that the sourceware tree generally requires autoconf-2.64, update
> the sim tree to require that too.
>
> This allows us to drop the long standing SIM_AC_COMMON/common.m4
> workaround as autoconf 2.64+ seems to work for me.
ping ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-09-29 2:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 23:48 [PATCH] " Mike Frysinger
2011-07-12 4:24 ` [PATCH v2] " Mike Frysinger
2011-09-29 2:01 ` Mike Frysinger [this message]
2011-10-10 2:44 ` Mike Frysinger
2011-10-17 17:26 ` [PATCH v2 resend] " Mike Frysinger
2011-10-17 17:30 ` Joel Brobecker
2011-10-17 16:50 ` [PATCH] " Joel Brobecker
2011-10-17 17:06 ` Mike Frysinger
2011-10-17 17:15 ` Joel Brobecker
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=201109282200.56083.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox