all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 44112@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#44112: SBCL is not reproducible
Date: Thu, 22 Oct 2020 13:19:08 +0200	[thread overview]
Message-ID: <CAJ3okZ3_oSeEBgrKxKKevch39KGHF0Orkyqqk9m5on2VwQNbTw@mail.gmail.com> (raw)
In-Reply-To: <87r1przfwo.fsf@yamatai>

Hi Guillaume,

Thank you for asking upstream.


On Wed, 21 Oct 2020 at 18:45, Guillaume Le Vaillant <glv@posteo.net> wrote:

> A developer of SBCL agrees that the timestamp should be removed [1], but
> currently Slime has a function depending on it. I asked if this could
> be fixed [2]. We'll see...
>
> [1] https://sourceforge.net/p/sbcl/mailman/message/37133640/

Ouch!  Hard to read when not subscribed. :-)

> [2] https://github.com/slime/slime/issues/583

If upstream does not want to patch, do you think it is doable to patch
SLIME and maintain the patch with the Guix package?

Thanks,
simon




  parent reply	other threads:[~2020-10-22 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zgcflzjn.fsf.ref@aol.com>
2020-10-21  8:12 ` bug#44112: SBCL is not reproducible zimoun
2020-10-21 12:41   ` Guillaume Le Vaillant
2020-10-21 13:37     ` zimoun
2020-10-21 13:43       ` zimoun
2020-10-21 14:32         ` Pierre Neidhardt
2020-10-21 15:13           ` zimoun
2020-10-21 16:45             ` Guillaume Le Vaillant
2020-10-21 16:55               ` Pierre Neidhardt
2020-10-22 11:19               ` zimoun [this message]
2020-10-22 12:13                 ` Pierre Neidhardt
2020-10-21 14:32     ` Pierre Neidhardt
2021-01-19 16:48     ` zimoun
2021-01-23  9:19       ` Guillaume Le Vaillant
2022-11-25 17:22   ` bug#44112: Hendursaga via Bug reports for GNU Guix
2022-12-09 18:50     ` bug#44112: zimoun

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=CAJ3okZ3_oSeEBgrKxKKevch39KGHF0Orkyqqk9m5on2VwQNbTw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=44112@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=mail@ambrevar.xyz \
    /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.