From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: Maxime Devos <maximedevos@telenet.be>, 57894@debbugs.gnu.org
Subject: [bug#57894] [PATCH 0/3] Minetest updates, new game.
Date: Thu, 22 Sep 2022 22:52:33 +0200 [thread overview]
Message-ID: <826777bc-5c75-ccb9-b6e0-9c3242d74749@interia.pl> (raw)
In-Reply-To: <8bc94893-89af-8d7d-c5ea-5f08bc99298d@telenet.be>
On 19.09.2022 19:00, Maxime Devos wrote:
>
>
> On 18-09-2022 01:14, Jan Wielkiewicz wrote:
>> I hope I adressed everything Maxime pointed out.
>> Both Minetest and Exile appear to be working.
>
> Addresses everything, thanks.
>
> Greetings,
> Maxime.
Minetest 5.6.1 is out but my commits haven't been merged yet.
Is there something wrong or are my changes queued in some way?
Usually my commits were merged once they were confirmed correct.
I think I will update minetest to 5.6.1 once my current commits are
merged to avoid merge conflicts.
Jan Wielkiewicz
next prev parent reply other threads:[~2022-09-22 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 23:14 [bug#57894] [PATCH 0/3] Minetest updates, new game Jan Wielkiewicz
2022-09-17 23:14 ` [bug#57896] [PATCH 1/3] gnu: minetest: update to 5.6.0 Jan Wielkiewicz
2022-09-17 23:14 ` [bug#57893] [PATCH 2/3] gnu: Add minetest-naturalslopeslib Jan Wielkiewicz
2022-09-18 11:26 ` bug#57893: Cancelling Jan Wielkiewicz
2022-09-17 23:14 ` [bug#57895] [PATCH 3/3] gnu: Add minetest-exile Jan Wielkiewicz
2022-09-18 11:29 ` [bug#57894] [PATCH 1/3] gnu: minetest: update to 5.6.0 Jan Wielkiewicz
2022-09-18 11:29 ` [bug#57894] [PATCH 2/3] gnu: Add minetest-naturalslopeslib Jan Wielkiewicz
2022-09-18 11:29 ` [bug#57894] [PATCH 3/3] gnu: Add minetest-exile Jan Wielkiewicz
2022-09-19 17:00 ` [bug#57894] [PATCH 0/3] Minetest updates, new game Maxime Devos
2022-09-22 20:52 ` Jan Wielkiewicz [this message]
2022-09-22 21:16 ` Maxime Devos
2022-09-22 22:09 ` Jan Wielkiewicz
2022-11-18 17:15 ` bug#57894: " Tobias Geerinckx-Rice 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=826777bc-5c75-ccb9-b6e0-9c3242d74749@interia.pl \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=57894@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).