all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "André A. Gomes" <andremegafone@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: glv@posteo.net, ludo@gnu.org, 66143@debbugs.gnu.org
Subject: [bug#66143] [PATCH]: Update emacs-slime and sbcl-slime-swank to 2.28-0.1e4b741
Date: Fri, 20 Oct 2023 22:46:48 +0300	[thread overview]
Message-ID: <87jzrhaxg7.fsf@gmail.com> (raw)
In-Reply-To: <875y3uob1g.fsf@gmail.com> ("André A. Gomes"'s message of "Thu, 28 Sep 2023 13:19:07 +0300")

André A. Gomes <andremegafone@gmail.com> writes:

> André A. Gomes <andremegafone@gmail.com> writes:
>
>> It makes no sense to have emacs-slime-next and cl-slime-swank-next.
>> I've bumped it because significant changes have been introduced since
>> the last tagged released.
>>
>> In the meantime, I've kindly request a tagged release upstream.  Whether
>> I'll get a reply soon remains to be seen.
>>
>> https://github.com/slime/slime/issues/792

The author ignored my kind request release.

I still think that it is not necessary to maintain both emacs-slime-next
and emacs-slime, but please help me to get this patch through.  Thanks.


-- 
André A. Gomes
"You cannot even find the ruins..."




  reply	other threads:[~2023-10-20 19:47 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 [this message]
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               ` [bug#66143] " Christopher Baines

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=87jzrhaxg7.fsf@gmail.com \
    --to=andremegafone@gmail.com \
    --cc=66143@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.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.