From: Guillaume Le Vaillant <glv@posteo.net>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 68096@debbugs.gnu.org
Subject: [bug#68096] [PATCH] gnu: cl-slime-swank: Update to 2.28-2.dfb83b4.
Date: Thu, 04 Jan 2024 09:42:12 +0000 [thread overview]
Message-ID: <87bka1wi0g.fsf@kitej> (raw)
In-Reply-To: <87462354e5b363438f31797bb81ceb66e9e682b4.1703848918.git.paul@apatience.com>
[-- Attachment #1: Type: text/plain, Size: 51 bytes --]
Shouldn't emacs-slime be updated at the same time?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-01-04 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 11:22 [bug#68096] [PATCH] gnu: cl-slime-swank: Update to 2.28-2.dfb83b4 Paul A. Patience
2024-01-04 9:42 ` Guillaume Le Vaillant [this message]
2024-03-20 12:31 ` bug#68096: " Guillaume Le Vaillant
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=87bka1wi0g.fsf@kitej \
--to=glv@posteo.net \
--cc=68096@debbugs.gnu.org \
--cc=paul@apatience.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).