All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Command documentation part 1.
Date: Tue, 26 Mar 2013 11:48:37 +0100	[thread overview]
Message-ID: <51517D05.10306@gmail.com> (raw)
In-Reply-To: <20130310204523.78d800fe@opensuse.site>

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

On 10.03.2013 17:45, Andrey Borzenkov wrote:

>> > Also I think it's worth mentioning that luks/geli/... aren't autoloaded.
>> > 
> Is there any other encryption container that is currently supported? I
> see only LUKS and geli.

Currently only luks and geli

>>> > > +When option @option{--check} is given, it points to a file that contains
>>> > > +list of @var{hash name} pairs. File hash and file name are separated by
>>> > > +single @key{SPACE} or @key{TAB}, one pair on a line. Option @option{--prefix}
>>> > > +may be used to give directory where files are located. Hash verification
>>> > > +stops after the first mismatch was found unless option @option{--keep-going}
>>> > > +was given.
>>> > > +@end deffn
>> > 
>> > This is the same format as used by standard UNIX tools.
>> > 
> Not sure what change is needed so left alone :)

Just a mention that it's the same format as UNIX tools

> +@deffn Command background_color color
> +Set background color for active terminal. For valid color specifications see
> +@pxref{Theme file format, ,Colors}. Background color can be changed only when
> +using @samp{gfxterm} for terminal output.
> +@end deffn

There is a confusion between the background behind the letters
(background_color_normal/_highlight variables) and solid color used as
background image (background_color command). This description would
probably suggest former rather than the latter.

Other than this patch is good.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2013-03-26 10:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 13:08 Command documentation policy Andrey Borzenkov
2013-01-22 17:12 ` Colin Watson
2013-01-22 17:16   ` Colin Watson
2013-01-29 10:25   ` Command documentation part 1 Andrey Borzenkov
2013-02-09 11:48     ` Francesco Lavra
2013-02-24  7:40       ` Andrey Borzenkov
2013-03-07 11:06         ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-03-08 11:45           ` Andrey Borzenkov
2013-03-10 16:45           ` Andrey Borzenkov
2013-03-26 10:48             ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-03-30  8:46               ` Andrey Borzenkov
2013-04-03  9:11                 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-05  7:41                   ` Andrey Borzenkov
2013-04-05  7:45                     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-05  7:57                       ` Andrey Borzenkov

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=51517D05.10306@gmail.com \
    --to=phcoder@gmail.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.