From: Baoquan He <bhe@redhat.com>
To: Jingbai Ma <jingbai.ma@hp.com>
Cc: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
kexec@lists.infradead.org
Subject: Re: [PATCH] makedumpfile: add missing options to man page or help
Date: Mon, 24 Jun 2013 11:11:43 +0800 [thread overview]
Message-ID: <51C7B8EF.6050002@redhat.com> (raw)
In-Reply-To: <51C40D7A.9070504@hp.com>
On 06/21/2013 04:23 PM, Jingbai Ma wrote:
>>>>>>
>>>>>> One of my solution is conversely to delete short options, and I don't
>>>>>> think it problem because the short options are only implicitly
>>>>>> exported
>>>>>> without explicit description on such as manual page and help message.
>>>>>
>>>>>
>>>>> Yeah, deleting short options is also a good method, let's wait and see
>>>>> what the maintainer say.
>>>>
>>>> I agree to delete short options.
>>>> Could you re-send the patch ?
>>>>
>>>
>>> BTW, we can assign non-printable characters as short options. Normally
>>> we don't type non-printable characters on console, so it's for free.
>>>
>>
>> Hi,
>> I think it's good idea. In kexec, some options use below short option
>> with a large value. With these indicative MACRO as short option, it will
>> make code more readable.
>>
>> Then all old short options can be replaced with them.
>>
>> #define OPT_MEM_MIN 256
>> #define OPT_MEM_MAX 257
>> #define OPT_REUSE_INITRD 258
>> #define OPT_LOAD_PRESERVE_CONTEXT 259
>> #define OPT_LOAD_JUMP_BACK_HELPER 260
>> #define OPT_ENTRY 261
>> #define OPT_MAX 262
>>
>
> But the value of char should only be from 0 to 255, so the value 256 to
> 262 couldn't be mapped to a single char.
As above discussion, printable short option is not needed, then it's
unnecessary to map value to a single char. Using short option just for
implementation.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-06-24 3:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 8:55 [PATCH] makedumpfile: add missing options to man page or help Baoquan He
2013-06-19 8:57 ` Baoquan He
2013-06-20 0:01 ` HATAYAMA Daisuke
2013-06-20 5:08 ` Baoquan
2013-06-20 6:43 ` Atsushi Kumagai
2013-06-20 8:03 ` Baoquan
2013-06-21 0:32 ` HATAYAMA Daisuke
2013-06-21 6:25 ` Baoquan
2013-06-21 7:31 ` Atsushi Kumagai
2013-06-21 8:23 ` Jingbai Ma
2013-06-24 3:11 ` Baoquan He [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=51C7B8EF.6050002@redhat.com \
--to=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jingbai.ma@hp.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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