From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: command line interface conventions and best practices
Date: Wed, 26 Feb 2020 10:56:54 -0500 [thread overview]
Message-ID: <EDBB9002-FDA0-4951-9671-5C01D9C34EE6@fuzziesquirrel.com> (raw)
Does anyone have a favorite reference that outlines de-facto command line
interface conventions and best practices? Things like e.g. long options
should have two dashes, options should not have capital letters, etc?
thanks!
-brad
next reply other threads:[~2020-02-26 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 15:56 Brad Bishop [this message]
2020-02-26 16:54 ` command line interface conventions and best practices Patrick Venture
2020-02-26 17:20 ` Patrick Williams
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=EDBB9002-FDA0-4951-9671-5C01D9C34EE6@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.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.