From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org
Cc: Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v3 1/2] build: specify minimum versions of gcc and binutils
Date: Thu, 11 Feb 2016 15:38:04 +0000 [thread overview]
Message-ID: <1455205084.814.68.camel@citrix.com> (raw)
In-Reply-To: <56BC9B7502000078000D108A@prv-mh.provo.novell.com>
On Thu, 2016-02-11 at 06:32 -0700, Jan Beulich wrote:
> > > > On 11.02.16 at 14:21, <ian.campbell@citrix.com> wrote:
> > On Thu, 2016-02-11 at 12:31 +0000, Andrew Cooper wrote:
> > > On 11/02/16 12:23, Ian Campbell wrote:
> > > > From: Doug Goldstein <cardoe@cardoe.com>
> > > >
> > > > To help people avoid having to figure out what versions of gcc and
> > > > binutils need to be supported document them explicitly.
> > > >
> > > > Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
> > > > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > >
> > > I would be tempted to abbreviate this to GCC 4.1 and Binutls 2.16,
> > > unless we specifically know of issues between the release and point
> > > releases.
> >
> > I don't mind doing this but if there is any quibbling at all about it
> > then
> > I would simply go with what is below.
>
> Yeah, I'd prefer the patches to go in as they're now: Both
> Acked-by: Jan Beulich <jbeulich@suse.com>
I have applied them both with you ack and Andy's R-by since he said "Either
way".
Thanks everyone.
prev parent reply other threads:[~2016-02-11 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 12:23 [PATCH v3 1/2] build: specify minimum versions of gcc and binutils Ian Campbell
2016-02-11 12:23 ` [PATCH v3 2/2] build: specify minimum versions of make Ian Campbell
2016-02-11 12:30 ` Andrew Cooper
2016-02-11 12:31 ` [PATCH v3 1/2] build: specify minimum versions of gcc and binutils Andrew Cooper
2016-02-11 13:21 ` Ian Campbell
2016-02-11 13:32 ` Jan Beulich
2016-02-11 15:38 ` Ian Campbell [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455205084.814.68.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).