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: Wed, 22 Sep 2021 20:43:55 +0200 [thread overview]
Message-ID: <7b49fa07477c7bcd898267b09980fd883e830519.camel@telenet.be> (raw)
In-Reply-To: <17d20f0f53dfe080278c7b52837b6e360cb3cffa.camel@planete-kraus.eu>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
Vivien Kraus schreef op wo 22-09-2021 om 20:37 [+0200]:
> Le mercredi 22 septembre 2021 à 20:15 +0200, Maxime Devos a écrit :
> > The latest patch you sent looks good to me, but I didn't test ti.
>
> I tested it by comparing the build of minetest-moreores when it fails
> because of the missing file and when it succeeds. Do you think it
> should be enough if it were to be tested that way?
That should be enough I think.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-09-22 19:17 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 [this message]
2021-10-14 15:14 ` Vivien Kraus via Bug reports for GNU Guix
2021-10-15 20:18 ` Maxime Devos
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=7b49fa07477c7bcd898267b09980fd883e830519.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.