public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/4690] getopt_long "--arg=val" and "--arg val" are not the same for "optional_argument" Date: Mon, 02 Jul 2007 15:39:00 -0000 [thread overview] Message-ID: <20070702153856.26096.qmail@sourceware.org> (raw) In-Reply-To: <20070622190036.4690.david@blue-labs.org> ------- Additional Comments From jakub at redhat dot com 2007-07-02 15:38 ------- Can you cite where you saw the two forms are interchangeable? E.g. man getopt: A long option normally begins with `--' followed by the long option name. If the option has a required argument, it may be written directly after the long option name, separated by `=', or as the next argument (ie. separated by whitespace on the command line). If the option has an optional argument, it must be written directly after the long option name, separated by `=', if present (if you add the `=' but nothing behind it, it is interpreted as if no argument was present; this is a slight bug, see the BUGS). -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://sourceware.org/bugzilla/show_bug.cgi?id=4690 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2007-07-02 15:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-22 19:00 [Bug libc/4690] New: " david at blue-labs dot org 2007-06-22 19:10 ` [Bug libc/4690] " drepper at redhat dot com 2007-06-22 19:17 ` david at blue-labs dot org 2007-06-22 19:21 ` [Bug manual/4690] " roland at gnu dot org 2007-06-22 19:22 ` roland at gnu dot org 2007-07-02 15:39 ` jakub at redhat dot com [this message] [not found] <bug-4690-131@http.sourceware.org/bugzilla/> 2012-04-08 9:51 ` aj at suse dot de 2014-02-16 19:20 ` jackie.rosen at hushmail dot com 2014-05-28 19:46 ` schwab at sourceware dot org 2014-05-28 19:47 ` schwab at sourceware dot org
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=20070702153856.26096.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).