grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Command documentation policy
Date: Tue, 22 Jan 2013 17:08:51 +0400	[thread overview]
Message-ID: <20130122170851.1bb50f87@opensuse.site> (raw)

Quit a number of commands are not documented. Is it intentional
(because they are not considered "user level API")? Should
documentation for them go into grub or grub-dev?


             reply	other threads:[~2013-01-22 13:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 13:08 Andrey Borzenkov [this message]
2013-01-22 17:12 ` Command documentation policy 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
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=20130122170851.1bb50f87@opensuse.site \
    --to=arvidjaar@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).