From: Guillaume Le Vaillant <glv@posteo.net>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 74527@debbugs.gnu.org
Subject: [bug#74527] [PATCH] gnu: cl-eclector: Update to 0.10.0.
Date: Tue, 26 Nov 2024 14:32:44 +0000 [thread overview]
Message-ID: <87sere9ib7.fsf@kitej> (raw)
In-Reply-To: <m17c8q5aza.fsf@fastmail.net> (Konrad Hinsen's message of "Tue, 26 Nov 2024 15:24:41 +0100")
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
>
>> It looks like the best solution is to update sbcl-common-lisp-jupyter as
>> well. Which unfortunately is not completely trivial because it has new
>> dependencies which are not yet packaged. I will look into this.
>
> Done. It was just one simple-to-package dependency.
>
> Now I have a three-part patch series. Should I submit is as a new patch,
> and close this one? Or submit it as an update to this patch, which now
> is the first one in a series ?
>
> Cheers,
> Konrad.
No need to create a new issue, you can just send the new patches to
<74527@debbugs.gnu.org> with titles like "[PATCH v2 1/3] gnu: ...",
"[PATCH v2 2/3] gnu: ..." etc.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-11-26 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 12:55 [bug#74527] [PATCH] gnu: cl-eclector: Update to 0.10.0 Konrad Hinsen
2024-11-26 13:08 ` Guillaume Le Vaillant
2024-11-26 13:57 ` Konrad Hinsen
2024-11-26 14:24 ` Konrad Hinsen
2024-11-26 14:32 ` Guillaume Le Vaillant [this message]
2024-11-26 15:44 ` [bug#74527] [PATCH v2 1/3] " Konrad Hinsen
2024-11-27 13:01 ` bug#74527: " Guillaume Le Vaillant
2024-11-26 15:45 ` [bug#74527] [PATCH v2 2/3] gnu: Add cl-nontrivial-gray-streams Konrad Hinsen
2024-11-26 15:45 ` [bug#74527] [PATCH v2 3/3] gnu: cl-common-lisp-jupyter: Update to 1.0 Konrad Hinsen
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=87sere9ib7.fsf@kitej \
--to=glv@posteo.net \
--cc=74527@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.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).