From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Kristian Lein-Mathisen" <kristianlein@gmail.com>
Cc: 57361@debbugs.gnu.org
Subject: [bug#57361] [PATCH] gnu: Add solvespace.
Date: Sat, 10 Sep 2022 17:27:03 +0200 [thread overview]
Message-ID: <8dec99c5a65ed093f26c5e0849e8936458bcc8f7.camel@gmail.com> (raw)
In-Reply-To: <87illygg8z.fsf_-_@gnu.org>
Am Donnerstag, dem 08.09.2022 um 15:14 +0200 schrieb Ludovic Courtès:
> Hi,
>
> Kristian Lein-Mathisen <kristianlein@gmail.com> skribis:
>
> > From a19e2d22f52b71db2ddc14b5dcaa6acb57c27484 Mon Sep 17 00:00:00
> > 2001
> > From: Kristian Lein-Mathisen <kristianlein@gmail.com>
> > Date: Mon, 5 Sep 2022 21:49:03 +0200
> > Subject: [PATCH 1/2] gnu: Add mimalloc.
> >
> > * gnu/packages/c.scm (mimalloc): New variable.
>
> [...]
>
> > From a2967120d10320962a0298caa412d320bca7804a Mon Sep 17 00:00:00
> > 2001
> > From: Kristian Lein-Mathisen <kristianlein@gmail.com>
> > Date: Tue, 6 Sep 2022 10:24:01 +0200
> > Subject: [PATCH 2/2] gnu: Add solvespace.
> >
> > * gnu/packages/engineering.scm (solvespace): New variable.
>
> Applied both, the latter with the cosmetic changes below.
Should we mark this as done then?
next prev parent reply other threads:[~2022-09-10 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 12:08 [bug#57361] [PATCH] gnu: Add solvespace Kristian Lein-Mathisen
2022-08-31 18:51 ` [bug#57361] Solvespace package re-done Kristian Lein-Mathisen
2022-09-01 17:18 ` Liliana Marie Prikler
2022-09-01 17:20 ` Liliana Marie Prikler
2022-09-05 19:57 ` [bug#57361] [PATCH] gnu: Add solvespace Kristian Lein-Mathisen
2022-09-06 8:30 ` Kristian Lein-Mathisen
2022-09-06 8:33 ` Kristian Lein-Mathisen
2022-09-08 13:14 ` Ludovic Courtès
2022-09-10 15:27 ` Liliana Marie Prikler [this message]
2022-09-11 14:13 ` bug#57361: " Ludovic Courtès
2022-09-10 7:55 ` [bug#57361] " ( via Guix-patches via
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=8dec99c5a65ed093f26c5e0849e8936458bcc8f7.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=57361@debbugs.gnu.org \
--cc=kristianlein@gmail.com \
--cc=ludo@gnu.org \
/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).