From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Install_c merge intention
Date: Sat, 16 Nov 2013 23:52:25 +0400 [thread overview]
Message-ID: <20131116235225.133d6fcf@opensuse.site> (raw)
In-Reply-To: <527E2FBD.6060501@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
В Sat, 09 Nov 2013 13:51:09 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> Hello, all. install_c is feature complete and I intent to make it
> upstream unless issues are raised until 16 Nov. It's available under
> http://git.savannah.gnu.org/cgit/grub.git/log/?h=phcoder/install_c
>
Hmm ... I noticed that you set quite a number of options as
OPTION_HIDDEN. That is fine, they are not meant for everyday use, but
how should users become aware of them? Read the source is not really the
option here (oops, pun unintended). They are not documented in grub.info
either.
I hoped arpg provides some way to show them (--help-all or similar) but
apparently not.
Those options were shown before so it can be considered regression.
Any ideas how to handle this?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-16 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 12:51 Install_c merge intention Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 4:58 ` Andrey Borzenkov
2013-11-10 13:33 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 14:26 ` [PATCH] fix qsort invocation in grub-install Andrey Borzenkov
2013-11-10 14:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-10 14:52 ` Install_c merge intention Andrey Borzenkov
2013-11-10 15:38 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-11 17:15 ` Andrey Borzenkov
2013-11-16 19:52 ` Andrey Borzenkov [this message]
2013-11-16 19:57 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-16 20:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-02 19:09 ` Jonathan McCune
2013-12-02 19:18 ` 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=20131116235225.133d6fcf@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).