From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] refresh: Add '--list-updaters' option.
Date: Sun, 25 Oct 2015 22:46:08 +0100 [thread overview]
Message-ID: <87611uk4f3.fsf@gnu.org> (raw)
In-Reply-To: <87611z9v27.fsf@gmail.com> (Alex Kost's message of "Thu, 22 Oct 2015 11:17:04 +0300")
Alex Kost <alezost@gmail.com> skribis:
> From 6d82f6384902e7de837a4dbfc86c524dbfd9145a Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost@gmail.com>
> Date: Thu, 22 Oct 2015 10:51:17 +0300
> Subject: [PATCH] refresh: Add '--list-updaters' option.
>
> * guix/scripts/refresh.scm (list-updaters-and-exit): New procedure.
> (%options, show-help): Add '--list-updaters' option.
> * doc/guix.texi (Invoking guix refresh): Document it.
[...]
> +@item --list-updaters
> +@itemx -L
> +List available updaters and exit.
Maybe add: “(see @option{--type} below.)”
OK to push with this change!
To make it even more useful, I wonder if we should add a ‘description’
field to updaters.
The best way to do that would probably be by definition
<upstream-updater> with ‘define-record-type*’ (because ‘description’ is
a known keyword for xgettext, as per po/guix/Makevars.)
WDYT?
Ludo’.
next prev parent reply other threads:[~2015-10-25 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 8:17 [PATCH] refresh: Add '--list-updaters' option Alex Kost
2015-10-25 21:46 ` Ludovic Courtès [this message]
2015-10-26 19:28 ` [PATCH] upstream: Add 'description' field to 'upstream-updater' Alex Kost
2015-10-27 17:26 ` Ludovic Courtès
2015-10-27 18:59 ` Alex Kost
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87611uk4f3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).