all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tristan Cottam via Guix-patches via <guix-patches@gnu.org>
To: "67009@debbugs.gnu.org" <67009@debbugs.gnu.org>
Subject: [bug#67009] [PATCH] build: minetest-build-system: Improve white space handling in mod name field.
Date: Fri, 10 Nov 2023 00:59:25 +0000	[thread overview]
Message-ID: <52GWSEkIAfwhhC3Omu3CYqBOZI0D5c0e2iyvQaGsvqhiLibFkuciScvZk-35eA_Z8rkRzbMKhuol0AxRvxgYdDLCnuAaXj3ipjq5-3j2YmE=@cott.am> (raw)
In-Reply-To: <Mw3bYJJXHCFsjOsi55NNrXMbnVGn8S8dqIzUwDUcpTaOrojg_PH0ZA6cyFHFdvg3DYyD7xeC2qYfwRAMpIGH993rnCvDDdr9-Q0yGtE-r3c=@cott.am>

The only mods I encountered with this problem aren't packaged upstream yet, I only have them in my own channel. Should I contribute them first in order to refer to them by package name?




  parent reply	other threads:[~2023-11-10  1:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09  1:33 [bug#67009] [PATCH] build: minetest-build-system: Improve white space handling in mod name field Tristan Cottam via Guix-patches via
2023-11-09  6:06 ` Liliana Marie Prikler
2023-11-09  6:06   ` Liliana Marie Prikler
2023-11-09 10:43 ` [bug#67009] [PATCH v2] " Tristan Cottam via Guix-patches via
2023-11-09 11:19   ` Liliana Marie Prikler
2023-11-09 12:18 ` [bug#67009] [PATCH v3] " Tristan Cottam via Guix-patches via
2023-11-09 13:06   ` Liliana Marie Prikler
     [not found]     ` <Mw3bYJJXHCFsjOsi55NNrXMbnVGn8S8dqIzUwDUcpTaOrojg_PH0ZA6cyFHFdvg3DYyD7xeC2qYfwRAMpIGH993rnCvDDdr9-Q0yGtE-r3c=@cott.am>
2023-11-10  0:59       ` Tristan Cottam via Guix-patches via [this message]
2023-11-10 17:54         ` [bug#67009] [PATCH] " Liliana Marie Prikler
2023-11-11  1:05 ` [bug#67009] [PATCH v4] " Tristan Cottam via Guix-patches via
2023-11-11  6:13   ` bug#67009: " Liliana Marie Prikler

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='52GWSEkIAfwhhC3Omu3CYqBOZI0D5c0e2iyvQaGsvqhiLibFkuciScvZk-35eA_Z8rkRzbMKhuol0AxRvxgYdDLCnuAaXj3ipjq5-3j2YmE=@cott.am' \
    --to=guix-patches@gnu.org \
    --cc=67009@debbugs.gnu.org \
    --cc=tristan@cott.am \
    /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.