unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 54454-done@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Leo Famulari <leo@famulari.name>
Subject: [bug#54454] [PATCH v2] ui: Describe package outputs.
Date: Mon, 05 Sep 2022 09:25:53 +0200	[thread overview]
Message-ID: <87zgfe5lku.fsf@gnu.org> (raw)
In-Reply-To: <86y1v0wzpm.fsf@gmail.com> (zimoun's message of "Sat, 03 Sep 2022 11:53:57 +0200")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Fri, 02 Sep 2022 at 19:14, Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
>
>>> --8<---------------cut here---------------start------------->8---
>>> $ guix show git |head -10
>>> name: git
>>> version: 2.37.2
>>> outputs:
>>> + send-email: see Appendix H
>>> + svn: see Appendix H
>>> + credential-netrc: see Appendix H
>>> + credential-libsecret: see Appendix H
>>> + subtree: see Appendix H
>>> + gui: see Appendix H
>>> + out: everything else
>>> --8<---------------cut here---------------end--------------->8---
>>> 
>>> Where can I see Appendix H though?  (Real question.)
>>
>> There is no appendix H, it's an obscure reference to the appendix H of
>> the x86 instruction set (containing undocumented instructions or here
>> undocumented outputs 🙂️).

Oooh, I see.  :-)

> +      (assoc-ref `(("bin" . ,(G_ "executable programs and scripts"))
> +                   ("debug" . ,(G_ "debug information"))
> +                   ("lib" . ,(G_ "shared libraries"))
> +                   ("static" . ,(G_ "static libraries"))
> +                   ("out" . ,(G_ "everything else")))
> +                 output)
> +      (G_ "see Appendix H"))))
>
> Maybe we could just replace this “see Appendix H” by “undocumented”.

+1!  For those like me who’d otherwise take it at face value.

Thanks,
Ludo’.




      reply	other threads:[~2022-09-05  7:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 19:16 [bug#54454] [PATCH] ui: Describe package outputs Liliana Marie Prikler
2022-03-18 20:12 ` Maxime Devos
2022-03-18 20:23   ` Liliana Marie Prikler
2022-03-18 20:16 ` Maxime Devos
2022-03-18 20:25   ` Liliana Marie Prikler
2022-03-18 20:50     ` Maxime Devos
2022-03-18 20:54 ` Maxime Devos
2022-03-18 22:24   ` Liliana Marie Prikler
2022-03-18 22:57     ` Maxime Devos
2022-03-18 23:27       ` Liliana Marie Prikler
2022-03-19  8:56         ` Maxime Devos
2022-03-19 10:48           ` Ludovic Courtès
2022-03-19 16:24 ` Leo Famulari
2022-06-26 12:37 ` [bug#54454] [PATCH v2] " Liliana Marie Prikler
2022-08-16 19:37   ` bug#54454: " Liliana Marie Prikler
2022-09-02 17:07     ` [bug#54454] " Ludovic Courtès
2022-09-02 17:14       ` Liliana Marie Prikler
2022-09-03  9:53         ` zimoun
2022-09-05  7:25           ` Ludovic Courtès [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

  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=87zgfe5lku.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54454-done@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=liliana.prikler@gmail.com \
    --cc=maximedevos@telenet.be \
    --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 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).