All of lore.kernel.org
 help / color / mirror / Atom feed
From: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
To: bhe@redhat.com
Cc: d.hatayama@jp.fujitsu.com, kexec@lists.infradead.org
Subject: Re: [PATCH] makedumpfile: add missing options to man page or help
Date: Thu, 20 Jun 2013 15:43:34 +0900	[thread overview]
Message-ID: <20130620154334.33a09ca47ec66a1c834db08e@mxc.nes.nec.co.jp> (raw)
In-Reply-To: <51C28E41.2080903@redhat.com>

Hello Baoquan and HATAYAMA-san,

On Thu, 20 Jun 2013 13:08:17 +0800
Baoquan <bhe@redhat.com> wrote:

> On 06/20/2013 08:01 AM, HATAYAMA Daisuke wrote:
> 
> > 
> >> makedumpfile has some options which has two 2 forms, long option
> >> and short option. E.g. --help  |  -h
> >>
> >> In man page and help, only one of them are presented, user may complain
> >> of this. Here add missing options.
> >>
> > 
> > I guess the maintainer does so intentionally, I'm not sure of course.
> > Characters for short options is limited resource, but now makedumpfile
> > has considerably many options. We can no longer assign reasonable
> > letters to each functionality with short options. For example, please
> > look at the definition of longopts:

That's right, some letters assigned to recent feature have no reason.
So, they aren't suitable to be exported explicitly for users.

> > 
> > static struct option longopts[] = {
> >         {"split", no_argument, NULL, 's'},
> >         {"reassemble", no_argument, NULL, 'r'},
> >         {"xen-syms", required_argument, NULL, 'y'},
> >         {"xen-vmcoreinfo", required_argument, NULL, 'z'},
> >         {"xen_phys_start", required_argument, NULL, 'P'},
> >         {"message-level", required_argument, NULL, 'm'},
> >         {"vtop", required_argument, NULL, 'V'},
> >         {"dump-dmesg", no_argument, NULL, 'M'},
> >         {"config", required_argument, NULL, 'C'},
> >         {"help", no_argument, NULL, 'h'},
> >         {"diskset", required_argument, NULL, 'k'},
> >         {"non-cyclic", no_argument, NULL, 'Y'},
> >         {"cyclic-buffer", required_argument, NULL, 'Z'},
> >         {"eppic", required_argument, NULL, 'S'},
> >         {"map-size", required_argument, NULL, 'A'},
> >         {0, 0, 0, 0}
> > };
> > 
> > I don't see any relationship on the last three options: non-cyclic vs Y,
> > cyclic-buffer vs Z, eppic vs S and map-size vs A. I don't think there
> > are users who use short options for these features.
> 
> 
> Hi,
> 
> Thanks for telling. I totally understand that unmarched letters between
> long and short options are truly annoying. But like current code, only
> presenting long options in man page and help may cause complaint from QA
> or customers.
> 
> > 
> > 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 ?


Thanks
Atsushi Kumagai

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2013-06-20  6:45 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 [this message]
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

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=20130620154334.33a09ca47ec66a1c834db08e@mxc.nes.nec.co.jp \
    --to=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=bhe@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=kexec@lists.infradead.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.