From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 63330-done@debbugs.gnu.org
Subject: bug#63330: [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think!
Date: Sun, 14 May 2023 12:31:00 +0200 [thread overview]
Message-ID: <15c6ca037bd90c11e0267dbd02935dff5b1aef9d.camel@gmail.com> (raw)
In-Reply-To: <87cz373st6.fsf@gmail.com>
Am Donnerstag, dem 11.05.2023 um 15:23 +0200 schrieb Simon Tournier:
> Maybe a comment would be helpful to remember that answer. :-)
Point taken.
Pushed the series with a follow-up commit to add said comment.
Cheers
next prev parent reply other threads:[~2023-05-14 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 16:04 [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Liliana Marie Prikler
2023-05-06 13:41 ` [bug#63330] [PATCH 2/4] gnu: Add immer Liliana Marie Prikler
2023-05-07 15:30 ` [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Maxim Cournoyer
2023-05-07 15:51 ` Liliana Marie Prikler
2023-05-07 17:12 ` Maxim Cournoyer
2023-05-07 19:40 ` Liliana Marie Prikler
2023-05-06 13:43 ` [bug#63330] [PATCH 3/4] gnu: Add zug Liliana Marie Prikler
2023-05-07 15:25 ` [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Maxim Cournoyer
2023-05-06 13:43 ` [bug#63330] [PATCH 4/4] gnu: Add lager Liliana Marie Prikler
2023-05-07 15:34 ` [bug#63330] [PATCH 0/4] Functional programming? In my C++?! It's more likely than you think! Maxim Cournoyer
2023-05-07 15:57 ` Liliana Marie Prikler
2023-05-07 17:10 ` Maxim Cournoyer
2023-05-11 13:23 ` Simon Tournier
2023-05-14 10:31 ` Liliana Marie Prikler [this message]
2023-05-06 13:51 ` [bug#63330] [PATCH 1/4] gnu: Add c-rrb Liliana Marie Prikler
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=15c6ca037bd90c11e0267dbd02935dff5b1aef9d.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=63330-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.