From: Maxime Devos <maximedevos@telenet.be>
To: Vivien Kraus <vivien@planete-kraus.eu>, 50677@debbugs.gnu.org
Subject: bug#50677: [PATCH] Minetest basic_materials really depends on moreores
Date: Fri, 15 Oct 2021 20:18:02 +0000 [thread overview]
Message-ID: <212dfdb8c6dfdf33b9d3fa793fc875b313da8433.camel@telenet.be> (raw)
In-Reply-To: <b4bc3bd85e3f0b9dddafd86f7278df6a78b0bcf5.camel@planete-kraus.eu>
Vivien Kraus schreef op do 14-10-2021 om 17:14 [+0200]:
> On IRC you said that you did one test. Aside from you, it seems that
> noone cares about minetest.
>
> Would you accept this patch? [...]
IIRC, I tested the patch, it worked, and it looked good to me.
However, I'm not a committer.
Anyway, I won't be working on Guix for a while (and I've unsubscribed
from the mailing lists) (though I intend to continue eventually), so I
won't be available for (minetest-related) reviews.
Greetings,
Maxime
--
The computer I'm typing this on doesn't have the secret key,
so the e-mail isn't signed.
next prev parent reply other threads:[~2021-10-15 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 15:23 bug#50677: [PATCH] Minetest basic_materials really depends on moreores Vivien Kraus via Bug reports for GNU Guix
2021-09-19 17:40 ` Maxime Devos
2021-09-19 18:54 ` Vivien Kraus via Bug reports for GNU Guix
2021-09-19 18:59 ` Vivien Kraus via Bug reports for GNU Guix
2021-09-19 19:18 ` Maxime Devos
2021-09-19 19:11 ` Maxime Devos
2021-09-19 21:05 ` Vivien Kraus via Bug reports for GNU Guix
2021-09-22 16:46 ` Vivien Kraus via Bug reports for GNU Guix
2021-09-22 17:41 ` Maxime Devos
2021-09-22 18:04 ` Vivien Kraus via Bug reports for GNU Guix
2021-09-22 18:15 ` Maxime Devos
2021-09-22 18:37 ` Vivien Kraus via Bug reports for GNU Guix
2021-09-22 18:43 ` Maxime Devos
2021-10-14 15:14 ` Vivien Kraus via Bug reports for GNU Guix
2021-10-15 20:18 ` Maxime Devos [this message]
2021-10-16 15:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=212dfdb8c6dfdf33b9d3fa793fc875b313da8433.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=50677@debbugs.gnu.org \
--cc=vivien@planete-kraus.eu \
/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.