From: David Laight <David.Laight@ACULAB.COM>
To: 'Masahiro Yamada' <yamada.masahiro@socionext.com>,
Kees Cook <keescook@chromium.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>, Arnd Bergmann <arnd@arndb.de>,
Greg KH <gregkh@linuxfoundation.org>,
Jessica Yu <jeyu@kernel.org>,
Lucas De Marchi <lucas.de.marchi@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Michal Marek <michal.lkml@markovi.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH] kbuild: check uniqueness of basename of modules
Date: Thu, 16 May 2019 09:00:50 +0000 [thread overview]
Message-ID: <5e6999f3d0b349bd86a32a612cff7b4b@AcuMS.aculab.com> (raw)
In-Reply-To: <CAK7LNARezpQgcK9O9K3ZFeebMVNroWStno_brvSLadsKXVfm-Q@mail.gmail.com>
From: Masahiro Yamada
> Sent: 15 May 2019 18:55
...
> > xargs basename -a -- | sort | ...
>
> Sorry for my ignorance, but could you
> teach me the effect of "--" ?
>
> I sometimes use "--" as a separator
> when there is ambiguity in arguments
> for example, "git log <revision> -- <path>"
>
> In this case, what is intended by "--"?
The '--' stops getopt() from parsing any more parameters.
Useful things like 'grep -- -q' which will search for the
string '-q' rather than treating it as a command line option.
This is all made more horrid by a decision by the writers
of glibc getopt() to 'permute' argv[] so that 'options'
can follow 'nonoptions' ie it converts:
prog file -arg
to
prog -arg file
The only program the historically allowed 'late' options
was 'rlogin hostname -l username'.
This is just broken.....
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-05-16 9:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 7:38 Masahiro Yamada
2019-05-15 7:53 ` Masahiro Yamada
2019-05-15 16:20 ` Kees Cook
2019-05-15 17:55 ` Masahiro Yamada
2019-05-15 18:38 ` Kees Cook
2019-05-17 3:39 ` Masahiro Yamada
2019-05-16 9:00 ` David Laight [this message]
2019-05-16 9:38 ` Masahiro Yamada
2019-05-15 8:08 ` Arnd Bergmann
2019-05-15 8:14 ` Greg KH
2019-05-15 8:57 ` Masahiro Yamada
2019-05-15 11:31 ` Greg KH
2019-05-15 11:42 ` Masahiro Yamada
2019-05-15 18:07 ` Masahiro Yamada
2019-05-15 18:31 ` Kees Cook
2019-05-17 3:37 ` Masahiro Yamada
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=5e6999f3d0b349bd86a32a612cff7b4b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=michal.lkml@markovi.net \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.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: 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
all inboxes | Powered by JetHome®