All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Alistair Francis <alistair.francis@wdc.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	alistair23@gmail.com
Subject: Re: [PATCH 1/3] config.sub: Update config.sub to latest version
Date: Thu, 16 May 2019 04:31:14 -0600	[thread overview]
Message-ID: <5CDD3BF2020000780022F8AD@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20190516000212.13468-1-alistair.francis@wdc.com>

>>> On 16.05.19 at 02:02, <alistair.francis@wdc.com> wrote:
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>

At least to me it is far from obvious why we would want/need to
do this update, or where the canonical "latest version" lives and
hence where this is coming from. Another question might be
whether it is a good thing to pull this in as a single blob (covering
a gap of 7 years), thus presumably also discarding authorship
of dozens of people. But of course, in the end it's the people
you've Cc-ed who need to decide whether this is fine to take in
this shape.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com>
To: "Alistair Francis" <alistair.francis@wdc.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	alistair23@gmail.com
Subject: Re: [Xen-devel] [PATCH 1/3] config.sub: Update config.sub to latest version
Date: Thu, 16 May 2019 04:31:14 -0600	[thread overview]
Message-ID: <5CDD3BF2020000780022F8AD@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190516103114.SALuPRhQqZ0lCS9ODjS7EBOqKPOMSOXvC5pXnOup0mk@z> (raw)
In-Reply-To: <20190516000212.13468-1-alistair.francis@wdc.com>

>>> On 16.05.19 at 02:02, <alistair.francis@wdc.com> wrote:
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>

At least to me it is far from obvious why we would want/need to
do this update, or where the canonical "latest version" lives and
hence where this is coming from. Another question might be
whether it is a good thing to pull this in as a single blob (covering
a gap of 7 years), thus presumably also discarding authorship
of dozens of people. But of course, in the end it's the people
you've Cc-ed who need to decide whether this is fine to take in
this shape.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-05-16 10:31 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  0:02 [PATCH 1/3] config.sub: Update config.sub to latest version Alistair Francis
2019-05-16  0:02 ` [Xen-devel] " Alistair Francis
2019-05-16  0:02 ` [PATCH 2/3] xen/drivers/char: Don't require vpl011 for all non-x86 archs Alistair Francis
2019-05-16  0:02   ` [Xen-devel] " Alistair Francis
2019-05-16 10:32   ` Jan Beulich
2019-05-16 10:32     ` [Xen-devel] " Jan Beulich
2019-05-16 19:30     ` Alistair Francis
2019-05-16 19:30       ` [Xen-devel] " Alistair Francis
2019-05-17  6:26       ` Jan Beulich
2019-05-17  6:26         ` [Xen-devel] " Jan Beulich
2019-05-17 22:02         ` Alistair Francis
2019-05-17 22:02           ` [Xen-devel] " Alistair Francis
2019-05-17  8:46       ` Julien Grall
2019-05-17  8:46         ` [Xen-devel] " Julien Grall
2019-05-17 22:01         ` Alistair Francis
2019-05-17 22:01           ` [Xen-devel] " Alistair Francis
2019-05-20  9:56           ` Julien Grall
2019-05-20  9:56             ` [Xen-devel] " Julien Grall
2019-05-16  0:02 ` [PATCH 3/3] xen/rwlock: Include lib.h Alistair Francis
2019-05-16  0:02   ` [Xen-devel] " Alistair Francis
2019-05-16 10:34   ` Jan Beulich
2019-05-16 10:34     ` [Xen-devel] " Jan Beulich
2019-05-16 10:31 ` Jan Beulich [this message]
2019-05-16 10:31   ` [Xen-devel] [PATCH 1/3] config.sub: Update config.sub to latest version Jan Beulich
2019-05-16 11:13   ` Olaf Hering
2019-05-16 11:13     ` [Xen-devel] " Olaf Hering
2019-05-16 11:39     ` Wei Liu
2019-05-16 11:39       ` [Xen-devel] " Wei Liu
2019-05-16 11:44       ` Olaf Hering
2019-05-16 11:44         ` [Xen-devel] " Olaf Hering
2019-05-16 12:47         ` Wei Liu
2019-05-16 12:47           ` [Xen-devel] " Wei Liu
2019-05-16 13:18       ` Olaf Hering
2019-05-16 13:18         ` [Xen-devel] " Olaf Hering
2019-05-16 13:30         ` Wei Liu
2019-05-16 13:30           ` [Xen-devel] " Wei Liu
2019-05-16 19:27           ` Alistair Francis
2019-05-16 19:27             ` [Xen-devel] " Alistair Francis
2019-05-17 16:37             ` Wei Liu
2019-05-17 16:37               ` [Xen-devel] " Wei Liu
2019-05-17 22:38               ` Alistair Francis
2019-05-17 22:38                 ` [Xen-devel] " Alistair Francis
2019-05-18  9:51                 ` Wei Liu
2019-05-18  9:51                   ` [Xen-devel] " Wei Liu
2019-05-16 19:25   ` Alistair Francis
2019-05-16 19:25     ` [Xen-devel] " Alistair Francis
2019-05-17 16:37     ` Wei Liu
2019-05-17 16:37       ` [Xen-devel] " Wei Liu

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=5CDD3BF2020000780022F8AD@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=wei.liu2@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.