grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] document cmdpath environment variable
Date: Sat, 16 Nov 2013 13:51:22 +0100	[thread overview]
Message-ID: <52876A4A.3020003@gmail.com> (raw)
In-Reply-To: <1384579135-30778-1-git-send-email-arvidjaar@gmail.com>

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

Go ahead.
On 16.11.2013 06:18, Andrey Borzenkov wrote:
> ---
>  docs/grub.texi | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/docs/grub.texi b/docs/grub.texi
> index 0a9670f..de72d0c 100644
> --- a/docs/grub.texi
> +++ b/docs/grub.texi
> @@ -2989,6 +2989,7 @@ These variables have special meaning to GRUB.
>  * biosnum::
>  * check_signatures::
>  * chosen::
> +* cmdpath::
>  * color_highlight::
>  * color_normal::
>  * debug::
> @@ -3058,6 +3059,16 @@ the titles of each of the submenus starting from the top level followed by
>  the title of the menu entry itself, separated by @samp{>}.
>  
>  
> +@node cmdpath
> +@subsection cmdpath
> +
> +The location from which @file{core.img} was loaded as an absolute
> +directory name (@pxref{File name syntax}).  This is set by GRUB at
> +startup based on information returned by platform firmware.  Not every
> +platform provides this information and some may return only device
> +without path name.
> +
> +
>  @node color_highlight
>  @subsection color_highlight
>  
> 



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

      reply	other threads:[~2013-11-16 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16  5:18 [PATCH] document cmdpath environment variable Andrey Borzenkov
2013-11-16 12:51 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=52876A4A.3020003@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 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).