From: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 34848@debbugs.gnu.org
Subject: [bug#34848] [PATCH] Remove the last vestiges of GuixSD.
Date: Wed, 13 Mar 2019 20:46:41 +0100 [thread overview]
Message-ID: <87wol24kwu.fsf@nckx> (raw)
In-Reply-To: <20190313192945.30680-1-somebody@not-sent-or-endorsed-by.tobias.gr>
Guix,
Tobias Geerinckx-Rice wrote:
> [PATCH] Remove the last vestiges of GuixSD.
I'm running the test suite now, which on my laptop that means that
I won't find that one stupid typo until tomorrow.
Meanwhile: thoughts?
The longer ISO image volume names shouldn't pose a problem; the
limit's 32.
Kind regards,
T G-R
next prev parent reply other threads:[~2019-03-13 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 19:29 [bug#34848] [PATCH] Remove the last vestiges of GuixSD Tobias Geerinckx-Rice
2019-03-13 19:46 ` Tobias Geerinckx-Rice [this message]
[not found] ` <handler.34848.B.15525062264398.ack@debbugs.gnu.org>
2019-03-13 22:35 ` bug#34848: Acknowledgement ([PATCH] Remove the last vestiges of GuixSD.) Tobias Geerinckx-Rice
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=87wol24kwu.fsf@nckx \
--to=me@tobias.gr \
--cc=34848@debbugs.gnu.org \
/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).