public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/5513] New: info -help (MultiLevelCommand) does not understand -help passed to itself Date: Thu, 20 Dec 2007 11:28:00 -0000 [thread overview] Message-ID: <20071220112843.5513.pmuldoon@redhat.com> (raw) (fhpd) info -help Error: Unknown command: -help It (MultiLevelCommand) appears to be parsing -help as a command. Making MultiLevelCommand extend ParameterizedCommand seems make it cannibalize options meant for the sub-command ie info auxv -verbose in that instance it appears -verbose is being read as belonging to info, not auxv -- Summary: info -help (MultiLevelCommand) does not understand -help passed to itself Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: pmuldoon at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5513 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2007-12-20 11:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071220112843.5513.pmuldoon@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).