All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, Paul Durrant <paul@xen.org>,
	Nick Rosbrook <rosbrookn@gmail.com>, Wei Liu <wl@xen.org>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [XEN PATCH for-4.14 1/2] tools: Commit autoconf (2.69) output from Debian buster
Date: Mon, 22 Jun 2020 11:17:51 +0200	[thread overview]
Message-ID: <20200622091738.GA27631@aepfle.de> (raw)
In-Reply-To: <20200612151931.1083-2-ian.jackson@eu.citrix.com>

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

On Fri, Jun 12, Ian Jackson wrote:

> These files are in tree so that people can build (including from git)
> without needing recent autotools.

Do you know those people who can not possibly install the required (now 8year old) autoconf version?

Olaf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-06-22  9:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 11:05 libxl dirty in tree after libxl build Andrew Cooper
2020-06-12 14:12 ` Ian Jackson
2020-06-12 14:55   ` Paul Durrant
2020-06-12 15:13     ` Ian Jackson
2020-06-12 15:19     ` [XEN PATCH for-4.14 0/2] tools: Update/reset autogenerated files Ian Jackson
2020-06-18 15:48       ` Ian Jackson
2020-06-18 15:50         ` Paul Durrant
2020-06-19  9:46       ` Anthony PERARD
2020-06-12 15:19     ` [XEN PATCH for-4.14 1/2] tools: Commit autoconf (2.69) output from Debian buster Ian Jackson
2020-06-19  9:41       ` Anthony PERARD
2020-06-19 15:21         ` Ian Jackson
2020-06-22  9:17       ` Olaf Hering [this message]
2020-06-12 15:19     ` [XEN PATCH for-4.14 2/2] tools: Commit flex (2.6.4) & bison (3.3.2) " Ian Jackson
2020-06-18 16:48       ` Anthony PERARD

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=20200622091738.GA27631@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=ian.jackson@eu.citrix.com \
    --cc=paul@xen.org \
    --cc=rosbrookn@gmail.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=wl@xen.org \
    --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.