From: "Brian C. Lane" <bcl@redhat.com>
To: Phil Susi <psusi@ubuntu.com>
Cc: parted-devel@lists.alioth.debian.org, linux-raid@vger.kernel.org
Subject: Re: [parted-devel] [PATCH 1/2] Add nonfs partition type 0xda (#1263835)
Date: Fri, 9 Oct 2015 11:35:26 -0700 [thread overview]
Message-ID: <20151009183526.GT2984@lister.brianlane.com> (raw)
In-Reply-To: <5617F80C.5050407@ubuntu.com>
On Fri, Oct 09, 2015 at 01:23:24PM -0400, Phil Susi wrote:
> On 10/9/2015 12:21 PM, Brian C. Lane wrote:
> > I think their thinking is that 0x80 implies a filesystem.
> >
> > I really don't see any harm in adding it, if you don't want to use it,
> > don't.
>
> I don't like adding things that serve no purpose and only confuse users.
> People end up running around with their hair on fire asking which type
> they should use, and if it just doesn't bloody matter, why confuse them
> and make the manual longer by giving them the choice? Keep it simple.
>
> To put it another way, seeing the option there makes people think they
> need to use it for some reason, after all, why else would it be there?
> And if that isn't true, then you have just created FUD.
>
It does have purpose, as described in the bug. And most users won't pay
any attention to it. The vast majority of them care about 'boot' and
that's it.
--
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
prev parent reply other threads:[~2015-10-09 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1443654419-3714-1-git-send-email-bcl@redhat.com>
[not found] ` <560EB887.6060302@ubuntu.com>
[not found] ` <20151008214916.GK2984@lister.brianlane.com>
2015-10-09 15:02 ` [parted-devel] [PATCH 1/2] Add nonfs partition type 0xda (#1263835) Phil Susi
[not found] ` <5617D701.1010109-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
2015-10-09 16:21 ` Brian C. Lane
2015-10-09 17:23 ` [parted-devel] " Phil Susi
2015-10-09 18:35 ` Brian C. Lane [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=20151009183526.GT2984@lister.brianlane.com \
--to=bcl@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=parted-devel@lists.alioth.debian.org \
--cc=psusi@ubuntu.com \
/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