From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5 v2] suppot/download: add option parsing to the download wrapper
Date: Sun, 7 Dec 2014 13:04:38 +0100 [thread overview]
Message-ID: <20141207130438.35328feb@free-electrons.com> (raw)
In-Reply-To: <7f3140282a6843b4d229d873a1e7076573df9a2f.1417949583.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 7 Dec 2014 12:02:35 +0100, Yann E. MORIN wrote:
> +help() {
> + cat <<_EOF_
> +NAME
> + ${my_name} - downlaod wrapper for Buildroot
> +
> +SYNOPSIS
> + ${my_name} [OPTION]... -- [BACKEND OPTION]...
Why do you create help text that look like man pages? It is very
unusual, most Unix commands don't have a help text that look like a man
page.
I had the same reflexion on the mke2img thing.
> +DESCRIPTIOM
DESCRIPTION
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-07 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 11:02 [Buildroot] [PATCH 0/5 v2] pkg-download: check hashes before the download (branch yem/download-hash) Yann E. MORIN
2014-12-07 11:02 ` [Buildroot] [PATCH 1/5 v2] pkg-download: fix arguments to hash checking script Yann E. MORIN
2014-12-07 21:08 ` Thomas Petazzoni
2014-12-07 11:02 ` [Buildroot] [PATCH 2/5 v2] suppot/download: add option parsing to the download wrapper Yann E. MORIN
2014-12-07 12:04 ` Thomas Petazzoni [this message]
2014-12-07 11:02 ` [Buildroot] [PATCH 3/5 v2] pkg-download: check for already downloaded file in " Yann E. MORIN
2014-12-07 11:02 ` [Buildroot] [PATCH 4/5 v2] pkg-download: verify the hashes from " Yann E. MORIN
2014-12-07 23:10 ` Yann E. MORIN
2014-12-07 23:39 ` Yann E. MORIN
2014-12-07 11:02 ` [Buildroot] [PATCH 5/5 v2] pkg-download: check hashes for locally cached files Yann E. MORIN
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=20141207130438.35328feb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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