From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Tanguy LE CARROUR <tanguy@bioneland.org>,
Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: GNU/Hurd on real hardware
Date: Sat, 30 Nov 2024 12:20:57 +0100 [thread overview]
Message-ID: <b5de824c-7509-4472-be75-7efb2ddbab0d@elenq.tech> (raw)
In-Reply-To: <173296524021.18145.14669060034223492625@bioneland.org>
On 2024-11-30 12:14, Tanguy LE CARROUR wrote:
> `origin/keyring` exist and its last commit is f8868dd56bff0f282329a33abb62262b2fc584b6
> (add Ekaitz).
>
> The "good" news is that it doesn’t seem to be a bug related to the Hurd! 😁
Hehe
You never know...
next prev parent reply other threads:[~2024-11-30 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 17:57 GNU/Hurd on real hardware Gabriel Wicki
2024-11-29 18:18 ` Janneke Nieuwenhuizen
2024-11-30 11:14 ` Tanguy LE CARROUR
2024-11-30 11:20 ` Ekaitz Zarraga [this message]
2024-11-30 11:48 ` janneke
2024-12-01 16:34 ` Tanguy LE CARROUR
2024-11-30 15:00 ` Simon Tournier
2024-12-01 16:39 ` Tanguy LE CARROUR
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=b5de824c-7509-4472-be75-7efb2ddbab0d@elenq.tech \
--to=ekaitz@elenq.tech \
--cc=help-guix@gnu.org \
--cc=janneke@gnu.org \
--cc=tanguy@bioneland.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.
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).