From: George Dunlap <george.dunlap@eu.citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [Patch v3 0/2] Remove figlet from the source tree
Date: Mon, 25 Nov 2013 12:21:01 +0000 [thread overview]
Message-ID: <529340AD.9040904@eu.citrix.com> (raw)
In-Reply-To: <1385377211-20637-1-git-send-email-andrew.cooper3@citrix.com>
On 11/25/2013 11:00 AM, Andrew Cooper wrote:
> This series removes the hacked up version of figlet from our source tree.
>
> Patch 1 replaces the use of figlet in the build system.
>
> Patch 2 has been deliberately omitted for brevity. It consistes of removing
> "xen/tools/figlet/figlet" from .gitignore, and deleting all files in the
> directory "xen/tools/figlet/"
>
> The series as a whole can be found on the 'remove-figlet-v3' branch of
> http://xenbits.xen.org/git-http/people/andrewcoop/xen.git
>
> George:
> This is purely a build change, so I request that it be included for 4.4
It's not purely a build change -- figlet is not installed by default on
a number of distros (Ubuntu didn't have it); and on those systems, this
will silently change remove the figlet-like lettering from boot.
And in any case, a build change still introduces a risk (however small)
that there will be a bug in the build under certain distros /
configurations which will have to be fixed, and may slip the release.
Remember our criteria:
1. A bug-free release
2. An awesome release
3. An on-time release
Your freeze exception analyses tend to focus exclusively on #2 --
moreover, on the positives of your patch ("w00t, no crappy figlet fork
in-tree!") and not on the potential negatives ([User doesn't notice new
figlet requirement] "That's weird, why did the banner go away? It was
kind of cool."). Please stop and think carefully about *each* of the
criteria before making a recommendation.
From a release perspective, I think the benefits out-weigh the risks, so:
Release-acked-by: George Dunlap <george.dunlap@eu.citrix.com>
From a patch-review perspective: Although it's clear we need to remove
figlet from the tree, I'm afraid that the effect of this on most people
will simply be to have the banner silently disappear. There's no way we
could have something in the build that would prompt people, is there? I
can't really think of a non-intrusive way at the moment, but maybe
someone has some ideas...
-George
next prev parent reply other threads:[~2013-11-25 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 11:00 [Patch v3 0/2] Remove figlet from the source tree Andrew Cooper
2013-11-25 11:00 ` [Patch v3 1/2] xen/build: Use a distro version of figlet Andrew Cooper
2013-11-25 11:21 ` [Patch v3 0/2] Remove figlet from the source tree Ian Campbell
2013-11-25 11:23 ` Andrew Cooper
2013-11-25 12:21 ` George Dunlap [this message]
2013-11-25 12:25 ` Ian Campbell
2013-11-25 14:38 ` Ian Jackson
2013-11-25 19:45 ` Keir Fraser
2013-11-26 1:25 ` Matthew Daley
2013-11-26 8:35 ` Ian Campbell
2013-11-29 10:43 ` Ian Campbell
2013-11-29 20:15 ` Keir Fraser
2013-12-02 14:11 ` Ian Campbell
2013-11-25 14:38 ` Ian Jackson
2013-11-25 14:41 ` George Dunlap
2013-11-25 16:35 ` Ian Jackson
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=529340AD.9040904@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--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).