All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Rob Hoes <Rob.Hoes@citrix.com>, Don Slutz <dslutz@verizon.com>,
	xen-devel@lists.xenproject.org
Subject: Re: 4.4.0-rc3 tagged
Date: Tue, 11 Feb 2014 11:12:19 +0100	[thread overview]
Message-ID: <52F9F783.2040708@citrix.com> (raw)
In-Reply-To: <1392112851.26657.59.camel@kazak.uk.xensource.com>

On 11/02/14 11:00, Ian Campbell wrote:
> On Tue, 2014-02-11 at 10:56 +0100, Roger Pau Monné wrote:
>> On 11/02/14 10:41, Ian Campbell wrote:
>>> On Mon, 2014-02-10 at 18:53 -0500, Don Slutz wrote:
>>>> On 02/10/14 14:33, Roger Pau Monné wrote:
>>>>> Did you run aclocal before autoconf?
>>>
>>>> That did what was needed.
>>>
>>> For future reference you can just run ./autogen.sh at the top level and
>>> it does the right thing.
>>>
>>> (or if it doesn't I'd appreciate a patch to make it do the right thing)
>>
>> I think we have two options here if we want to add the check version
>> stuff, either we run aclocal before autoconf (and require the user to
>> have the autoconf-archive package) or we pick the AX_COMPARE_VERSION
>> macro source [0] and add it to our local m4/ folder.
> 
> Is it the case that we currently do the latter for al the existing
> checks?

Yes, but I'm not sure if any of the macros we have inside of m4/ are
also part of autoconf-archive (at least some of those are custom-made
AFAIK). I also think it's best to do the latter, I'm going to add the
macro itself to my patch and resend.

Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-02-11 10:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 12:14 4.4.0-rc3 tagged Ian Jackson
2014-01-31 23:07 ` Don Slutz
2014-02-03 11:48   ` Ian Jackson
2014-02-03 12:01     ` Stefano Stabellini
2014-02-07  0:15       ` Don Slutz
2014-02-07 10:05         ` Ian Campbell
2014-02-07 16:22           ` Don Slutz
2014-02-07 16:29             ` Andrew Cooper
2014-02-10  9:55               ` Ian Campbell
2014-02-10 10:59                 ` Roger Pau Monné
2014-02-10 18:48                   ` Don Slutz
2014-02-10 18:59                     ` Roger Pau Monné
2014-02-10 19:23                       ` Don Slutz
2014-02-10 19:33                         ` Roger Pau Monné
2014-02-10 23:53                           ` Don Slutz
2014-02-11  9:41                             ` Ian Campbell
2014-02-11  9:56                               ` Roger Pau Monné
2014-02-11 10:00                                 ` Ian Campbell
2014-02-11 10:12                                   ` Roger Pau Monné [this message]
2014-02-11 10:14                                     ` Ian Campbell
2014-02-11 16:31                                       ` Ian Jackson
2014-03-12 13:54                   ` Ian Campbell
2014-03-12 13:56                     ` Ian Campbell

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=52F9F783.2040708@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Rob.Hoes@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.