From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 44547@debbugs.gnu.org
Subject: [bug#44547] [PATCH 0/2] Fix "add" snippet and new "addcl" snippet for cumbersome Common Lisp packages
Date: Sat, 21 Nov 2020 12:03:53 +0100 [thread overview]
Message-ID: <87ft530y5i.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87sg93qda3.fsf@yamatai>
[-- Attachment #1: Type: text/plain, Size: 38 bytes --]
Good catch, I'll send a fix just now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-11-21 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 9:08 [bug#44547] [PATCH 0/2] Fix "add" snippet and new "addcl" snippet for cumbersome Common Lisp packages Pierre Neidhardt
2020-11-10 9:16 ` [bug#44547] [PATCH 1/2] etc: snippets: Fix package name extraction Pierre Neidhardt
2020-11-10 9:16 ` [bug#44547] [PATCH 2/2] etc: snippets: Prefill Common Lisp package names Pierre Neidhardt
[not found] ` <handler.44547.B.160499933824191.ack@debbugs.gnu.org>
2020-11-20 10:26 ` [bug#44547] Acknowledgement ([PATCH 0/2] Fix "add" snippet and new "addcl" snippet for cumbersome Common Lisp packages) Pierre Neidhardt
2020-11-21 9:17 ` [bug#44547] [PATCH 0/2] Fix "add" snippet and new "addcl" snippet for cumbersome Common Lisp packages Guillaume Le Vaillant
2020-11-21 11:03 ` Pierre Neidhardt [this message]
2020-11-21 11:05 ` [bug#44547] [PATCH v2 1/2] etc: snippets: Fix package name extraction Pierre Neidhardt
2020-11-21 11:05 ` [bug#44547] [PATCH v2 2/2] etc: snippets: Prefill Common Lisp package names Pierre Neidhardt
2020-11-21 11:11 ` [bug#44547] [PATCH v3 1/2] etc: snippets: Fix package name extraction Pierre Neidhardt
2020-11-21 11:11 ` [bug#44547] [PATCH v3 2/2] etc: snippets: Prefill Common Lisp package names Pierre Neidhardt
2020-11-21 12:43 ` Guillaume Le Vaillant
2020-11-23 10:16 ` Pierre Neidhardt
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=87ft530y5i.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=44547@debbugs.gnu.org \
--cc=glv@posteo.net \
/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.