From: Mathieu Othacehe <othacehe@gnu.org>
To: Martin Becze <mjbecze@riseup.net>
Cc: 43183-done@debbugs.gnu.org
Subject: bug#43183: [PATCH v2 3/5] gnu: Add guile-struct-pack.
Date: Thu, 10 Sep 2020 09:37:24 +0200 [thread overview]
Message-ID: <87blie5bgr.fsf@gnu.org> (raw)
In-Reply-To: <7583c236-9d0b-bb2c-51d7-0215c0bf57b9@riseup.net> (Martin Becze's message of "Tue, 8 Sep 2020 11:04:27 -0500")
Hello Martin,
> I apologize, I'm having a bit of difficultly with Emacs atm.
No worries! I fixed minor details and pushed.
Thanks,
--
Mathieu
https://othacehe.org
next prev parent reply other threads:[~2020-09-10 7:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:02 [bug#43183] [PATCH] gnu: Add loko-scheme Martin Becze
2020-09-04 6:43 ` Mathieu Othacehe
2020-09-04 6:49 ` Martin Becze
2020-09-04 7:16 ` Mathieu Othacehe
2020-09-04 7:33 ` Ricardo Wurmus
2020-09-04 20:25 ` [bug#43183] [PATCH v2 0/5] " Martin Becze
2020-09-04 20:25 ` [bug#43183] [PATCH v2 1/5] " Martin Becze
2020-09-04 20:25 ` [bug#43183] [PATCH v2 2/5] gnu: guile-pfds: When using Guile 3, compile as a r6rs library Martin Becze
2020-09-07 6:30 ` Mathieu Othacehe
2020-09-04 20:25 ` [bug#43183] [PATCH v2 3/5] gnu: Add guile-struct-pack Martin Becze
2020-09-07 6:30 ` Mathieu Othacehe
2020-09-08 16:04 ` Martin Becze
2020-09-10 7:37 ` Mathieu Othacehe [this message]
2020-09-04 20:25 ` [bug#43183] [PATCH v2 4/5] gnu: Add guile-machine-code Martin Becze
2020-09-04 20:25 ` [bug#43183] [PATCH v2 5/5] gnu: Add guile-laesare Martin Becze
2020-09-08 15:59 ` [bug#43183] [PATCH v3 0/4] Add loko-scheme Martin Becze
2020-09-08 15:59 ` [bug#43183] [PATCH v3 1/4] gnu: Add guile-struct-pack Martin Becze
2020-09-08 15:59 ` [bug#43183] [PATCH v3 2/4] gnu: Add guile-machine-code Martin Becze
2020-09-08 15:59 ` [bug#43183] [PATCH v3 3/4] gnu: Add guile-laesare Martin Becze
2020-09-08 15:59 ` [bug#43183] [PATCH v3 4/4] gnu: Add loko-scheme Martin Becze
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=87blie5bgr.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=43183-done@debbugs.gnu.org \
--cc=mjbecze@riseup.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).