From: Ricardo Wurmus <rekado@elephly.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 宋文武 <iyzsong@member.fsf.org>, 34959-done@debbugs.gnu.org
Subject: [bug#34959] Acknowledgement ([PATCH] Add Multiple Common Lisp Packages)
Date: Wed, 10 Apr 2019 20:19:28 +0200 [thread overview]
Message-ID: <87ef69en9r.fsf@elephly.net> (raw)
In-Reply-To: <87wok1oi9u.fsf@gmail.com>
Katherine Cox-Buday <cox.katherine.e@gmail.com> writes:
> As an aside, I don't know how much of this is obvious to other folks
> (i.e. maybe folks who contribute to GNU projects more often), but I feel
> like I've been discovering things like this which aren't in the Guix
> manual. Did I just miss this stuff (very possible!), or are we missing
> some instruction and perhaps links to GNU standards?
The “Contributing” section in the manual does link to the GNU standards
(if you’re reading this in an Info reader like Emacs you may want to
install the “gnu-standards” package to be able to follow the link
locally).
It also mentions the snippets and how to use them.
The Contributing section in the manual is pretty big, so it’s easy to
miss something.
--
Ricardo
prev parent reply other threads:[~2019-04-10 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 20:14 [bug#34959] [PATCH] Add Multiple Common Lisp Packages Katherine Cox-Buday
[not found] ` <handler.34959.B.155337211019624.ack@debbugs.gnu.org>
2019-03-23 20:41 ` [bug#34959] Acknowledgement ([PATCH] Add Multiple Common Lisp Packages) Katherine Cox-Buday
2019-03-24 10:01 ` Ricardo Wurmus
2019-03-28 17:38 ` Katherine Cox-Buday
2019-03-28 20:43 ` Ricardo Wurmus
2019-03-29 17:15 ` Katherine Cox-Buday
2019-03-29 23:19 ` Katherine Cox-Buday
2019-04-07 6:13 ` bug#34959: " 宋文武
2019-04-10 14:46 ` [bug#34959] " Katherine Cox-Buday
2019-04-10 17:00 ` Ricardo Wurmus
2019-04-10 17:57 ` Katherine Cox-Buday
2019-04-10 18:19 ` Ricardo Wurmus [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=87ef69en9r.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=34959-done@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.com \
--cc=iyzsong@member.fsf.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 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.