From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub cvs ... configfile
Date: Thu, 20 Apr 2006 05:26:43 +0200 [thread overview]
Message-ID: <200604200526.43870.okuji@enbug.org> (raw)
In-Reply-To: <ecf57e24f2d166b365552ed40a75bdde@penguinppc.org>
On Thursday 20 April 2006 04:53, Hollis Blanchard wrote:
> Offering multiple commands that do the same thing is not a good design
> philosphy, and from the other comments on this subject I know I'm not
> alone in that belief. No offense, but I don't think one developer
> liking it is a good enough reason.
I'm not alone, either. I have talked about this with my collegue in PUPA, and
he agreed with me.
I'd like to know why it is a bad phylosophy. In many systems, aliases are
often provided for convenience. Look at test and [. Look at true and :. Short
cuts are also a kind of aliases. I don't see anything wrong with this. "There
should be only one way to do a thing" is Python's phylosophy, but Perl
developers wouldn't agree with you.
Of course, "I like it" is not a good reason. But menuentry is too long to
type. This is good enough for me.
Okuji
prev parent reply other threads:[~2006-04-20 3:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 5:58 grub cvs ... configfile Jeff Chua
2006-04-02 11:30 ` Marco Gerards
2006-04-19 11:10 ` Jeff Chua
2006-04-19 11:16 ` Marco Gerards
2006-04-19 11:27 ` Jeff Chua
2006-04-19 13:12 ` Marco Gerards
2006-04-19 15:30 ` Jeff Chua
2006-04-19 16:24 ` Marco Gerards
2006-04-19 16:24 ` Vesa Jääskeläinen
2006-04-19 16:30 ` Hollis Blanchard
2006-04-19 16:35 ` Marco Gerards
2006-04-20 2:36 ` Yoshinori K. Okuji
2006-04-20 2:53 ` Hollis Blanchard
2006-04-20 3:26 ` Yoshinori K. Okuji [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=200604200526.43870.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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.