From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: Maxime Devos <maximedevos@telenet.be>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Updating minetest to 5.6.0?
Date: Sun, 18 Sep 2022 13:11:51 +0200 [thread overview]
Message-ID: <0195a026-d5c3-d769-6400-dca23cee60ea@interia.pl> (raw)
In-Reply-To: <a21ce318-9ce7-055a-0f1a-2f6374e3cbec@telenet.be>
On 17.09.2022 11:43, Maxime Devos wrote:
>
>
> On 17-09-2022 02:10, Jan Wielkiewicz wrote:
>> Done. See the patches (I can't really find "git send-email" on Guix
>> for some odd reason). The hacks in the Exile package are quite ugly,
>> but I don't know a better way, see below.
>>
>
> Try "guix show git", it will mention a 'send-email' output that you can
> install to have access to 'git send-email'. See ‘(guix)Packages with
> Multiple Outputs’ on how to install such outputs.
>
> Greetings,
> Maxime.
Okay, I believe I covered all your objections and my changes are good to
go now.
I sent a patch series to the guix-patches mailing list, unfortunately I
forgot to send subsequent patches to NNN@debbugs.gnu.org (It's almost 2
years since the last time I contributed anything to Guix).
Should I close these issues and send the series one more time properly
or should I skip it this time to avoid making even bigger mess?
Jan Wielkiewicz
next prev parent reply other threads:[~2022-09-18 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 17:59 Updating minetest to 5.6.0? Jan
2022-09-15 18:15 ` Maxime Devos
2022-09-15 18:27 ` Tobias Platen
2022-09-15 22:45 ` Jan
2022-09-16 8:59 ` Maxime Devos
2022-09-16 17:57 ` Jan Wielkiewicz
2022-09-16 18:18 ` Maxime Devos
2022-09-17 0:10 ` Jan Wielkiewicz
2022-09-17 0:13 ` Jan Wielkiewicz
2022-09-17 10:00 ` Maxime Devos
2022-09-17 9:43 ` Maxime Devos
2022-09-18 11:11 ` Jan Wielkiewicz [this message]
2022-09-18 11:41 ` Jan Wielkiewicz
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=0195a026-d5c3-d769-6400-dca23cee60ea@interia.pl \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=guix-devel@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 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.