From: Arun Isaac <arunisaac@systemreboot.net>
To: zimoun <zimon.toutoune@gmail.com>, jgart <jgart@dismail.de>,
59217@debbugs.gnu.org
Subject: [bug#59217] Acknowledgement ([PATCH] guix: lint: Improve message in linter warning.)
Date: Wed, 23 Nov 2022 12:52:51 +0000 [thread overview]
Message-ID: <87bkoxbzoc.fsf@systemreboot.net> (raw)
In-Reply-To: <86mt8iashd.fsf@gmail.com>
> Well, maybe a paragraph in the manual under ’(guix) Synopses and
> Descriptions’ is a better location for such explanations than the linter
> message itself. WDYT?
That sounds good. Detailed explanations do belong in the manual. But,
the linter CLI output should link to the relevant section of the web
manual. That would be better than sending people hunting in the
manual. Many good linters for other programming languages do do this.
Cheers!
next prev parent reply other threads:[~2022-11-23 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 15:09 [bug#59217] [PATCH] guix: lint: Improve message in linter warning jgart via Guix-patches via
[not found] ` <handler.59217.B.166826577117982.ack@debbugs.gnu.org>
2022-11-12 15:15 ` [bug#59217] Acknowledgement ([PATCH] guix: lint: Improve message in linter warning.) jgart via Guix-patches via
2022-11-22 20:58 ` Arun Isaac
2022-11-23 10:13 ` zimoun
2022-11-23 12:52 ` Arun Isaac [this message]
2023-03-21 19:50 ` [bug#59217] [PATCH] guix: lint: Improve message in linter warning Maxim Cournoyer
2023-03-22 21:22 ` Arun Isaac
2023-03-23 2:52 ` Maxim Cournoyer
2023-03-22 21:37 ` jgart via Guix-patches via
2022-11-19 18:37 ` Ludovic Courtès
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=87bkoxbzoc.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=59217@debbugs.gnu.org \
--cc=jgart@dismail.de \
--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).