From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 47466-done@debbugs.gnu.org
Subject: bug#47466: [PATCH] scripts: import: cran: Add missing help for 'style' option.
Date: Mon, 29 Mar 2021 19:57:49 +0100 [thread overview]
Message-ID: <87ft0d23f6.fsf@cbaines.net> (raw)
In-Reply-To: <20210329131117.6592-1-zimon.toutoune@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> * guix/scripts/import/cran.scm (show-help): Add help message for 'style'
> option.
> ---
> guix/scripts/import/cran.scm | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/guix/scripts/import/cran.scm b/guix/scripts/import/cran.scm
> index 4767bc082d..466d0cb8e2 100644
> --- a/guix/scripts/import/cran.scm
> +++ b/guix/scripts/import/cran.scm
> @@ -50,6 +50,9 @@ Import and convert the CRAN package for PACKAGE-NAME.\n"))
> (display (G_ "
> -r, --recursive import packages recursively"))
> (display (G_ "
> + -s SPECIFICATIONS, --style=SPECIFICATIONS
> + specify package specifications instead of references"))
> + (display (G_ "
> -V, --version display version information and exit"))
> (newline)
> (show-bug-report-information))
I changed the message, and pushed this as
55c25ee4c5cee0707c94f773eb7d1686f79cff75.
+ -s, --style=STYLE choose output style, either specification or variable"))
In my view, the thing in caps is a placeholder, so I put STYLE rather
than SPECIFICATIONS, I also altered the message to hint at what this
controls (the output), and the supported values.
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2021-03-29 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 13:11 [bug#47466] [PATCH] scripts: import: cran: Add missing help for 'style' option zimoun
2021-03-29 18:57 ` Christopher Baines [this message]
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=87ft0d23f6.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=47466-done@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.