From: Christopher Baines <mail@cbaines.net>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 66143-done@debbugs.gnu.org
Subject: [bug#66143] [PATCH]: Update emacs-slime and sbcl-slime-swank to 2.28-0.1e4b741
Date: Tue, 24 Oct 2023 14:08:28 +0100 [thread overview]
Message-ID: <87r0lk2mc4.fsf@cbaines.net> (raw)
In-Reply-To: <87a5s8kxa5.fsf@kitej>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Guillaume Le Vaillant <glv@posteo.net> writes:
> Patches applied as d62a613bcff726dfc835313064228e7bc3b7cda6 and
> following, with a completed commit message for the second patch.
I did raise an objection earlier in the thread to these changes being
merged. Not discussing (or even acknowledging issues raised) is
unhelpful.
Given what I've now read from upstream [1], I think it can be justified
in this case, but this is independent from the above. I think we still
should record reasons for deviating from the norm in comments (and
commit messages if useful).
1: https://github.com/slime/slime/issues/792
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2023-10-24 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:51 [bug#66143] [PATCH]: Update emacs-slime and sbcl-slime-swank to 2.28-0.1e4b741 André A. Gomes
2023-09-25 10:01 ` Christopher Baines
2023-09-26 9:16 ` André A. Gomes
2023-09-28 10:19 ` André A. Gomes
2023-10-20 19:46 ` André A. Gomes
2023-10-22 11:51 ` Guillaume Le Vaillant
2023-10-24 7:31 ` André A. Gomes
2023-10-24 12:40 ` bug#66143: " Guillaume Le Vaillant
2023-10-24 13:08 ` Christopher Baines [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=87r0lk2mc4.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=66143-done@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 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).