All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 2/2] Alias cls as clear
Date: Sat, 25 Jul 2009 18:21:15 +0200	[thread overview]
Message-ID: <20090725162115.GG12326@thorin> (raw)
In-Reply-To: <C7A50D1B-F2D2-4459-AC43-F892EA7A0BE3@gmail.com>

On Thu, Jul 23, 2009 at 04:05:00PM -0700, Joe Auricchio wrote:
>
> On 23 Jul, 2009, at 15:42 , Pavel Roskin wrote:
>> On Wed, 2009-07-22 at 22:08 -0700, Joe Auricchio wrote:
>>> * commands/minicmd.c: Add clear as alias for cls.
>>>
>>> My background is in Unix, so 'clear' comes much more naturally to my
>>> fingers than 'cls'. But it's bad to clutter grub with too many  
>>> commands.
>>> So I leave this to the maintainers: do we add both commands, only  
>>> one,
>>> or
>>> neither?
>>
>> Let's have "clear" only, as it's more clear :-)
>>
>> Please include the ChangeLog entry.
>
>
> How's this?

The ChangeLog entry is incomplete.  It should be e.g.:

	* commands/minicmd.c (grub_mini_cmd_clear): New function.

etc.  See other entries as an example.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-07-25 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  5:08 [PATCH 2/2] Alias cls as clear Joe Auricchio
2009-07-23 22:42 ` Pavel Roskin
2009-07-23 23:05   ` Joe Auricchio
2009-07-25 16:21     ` Robert Millan [this message]
2009-07-29  5:58       ` Joe Auricchio
2009-07-31 15:57         ` Robert Millan
2009-11-19 10:42         ` Robert Millan
2009-07-25 16:15   ` Robert Millan

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=20090725162115.GG12326@thorin \
    --to=rmh@aybabtu.com \
    --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.