all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Faiz via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, 64362@debbugs.gnu.org
Cc: iyzsong@envs.net
Subject: [bug#64362] [PATCH 3/3] gnu: Add mc2mt.
Date: Sat, 1 Jul 2023 11:20:55 +0800	[thread overview]
Message-ID: <fa948fc4-a15b-0159-1072-2d2063f8f6fa@disroot.org> (raw)
In-Reply-To: <43ba5dee30a02e26492f0ae8b29946bf88d9e652.camel@gmail.com>

On 7/1/23 02:23, Liliana Marie Prikler wrote:
> Am Freitag, dem 30.06.2023 um 17:34 +0800 schrieb Adam Faiz:
> This snippet looks like you really want to write a patch or two.
You're right, I should have done it as a patch, but I didn't because I don't know how to use
commit message templates for Guix commits.
I always check similiar commits and paste the commit message as a template which is tedious.

>> +    (build-system pyproject-build-system)
>> +    (propagated-inputs (list python-anvil-parser))
>> +    (arguments
>> +     (list #:tests? #f)) ; no tests
>> +    (synopsis "Minecraft to Minetest world converter")
>> +    (description "@code{mc2mt} is a Minecraft to Minetest world
>> converter.
>> +It can convert worlds from Minecraft 1.9 and later.")
>> +    (home-page "https://github.com/listia/mc2mt")
>> +    (license license:expat))))
>> +
> I think we should tone down on the usage of "Minecraft" in synopses and
> descriptions.  In particular for the dependencies it ought to describe
> the file formats without referring to the program that produces them.
Alright.

> Cheers





  reply	other threads:[~2023-07-01  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  9:10 [bug#64362] [PATCH 0/3] gnu: Add mc2mt Adam Faiz via Guix-patches via
2023-06-30  9:21 ` [bug#64362] [PATCH 1/3] gnu: Add python-nbt Adam Faiz via Guix-patches via
2023-06-30  9:22   ` [bug#64362] [PATCH 2/3] gnu: Add python-anvil-parser Adam Faiz via Guix-patches via
2023-06-30  9:34     ` [bug#64362] [PATCH 3/3] gnu: Add mc2mt Adam Faiz via Guix-patches via
2023-06-30 18:23       ` Liliana Marie Prikler
2023-07-01  3:20         ` Adam Faiz via Guix-patches via [this message]
2023-07-01  5:31           ` Liliana Marie Prikler
2023-07-01 11:40             ` [bug#64362] [PATCH v1 1/3] gnu: Add python-nbt Adam Faiz via Guix-patches via
2023-07-01 11:42               ` [bug#64362] [PATCH v1 2/3] gnu: Add python-anvil-parser Adam Faiz via Guix-patches via
2023-07-01 11:44                 ` [bug#64362] [PATCH v1 3/3] gnu: Add mc2mt Adam Faiz via Guix-patches via
2023-07-01 14:14 ` Adam Faiz 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa948fc4-a15b-0159-1072-2d2063f8f6fa@disroot.org \
    --to=guix-patches@gnu.org \
    --cc=64362@debbugs.gnu.org \
    --cc=adam.faiz@disroot.org \
    --cc=iyzsong@envs.net \
    --cc=liliana.prikler@gmail.com \
    /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.