unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andreas Enge <andreas@enge.fr>,  guix-devel@gnu.org
Subject: Re: [PATCH 1/2] teams: Add hurd team.
Date: Sun, 15 Dec 2024 08:59:40 +0100	[thread overview]
Message-ID: <875xnlfkb7.fsf@gnu.org> (raw)
In-Reply-To: <87h675kejc.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 15 Dec 2024 00:53:11 +0100")

Ludovic Courtès writes:

> Janneke Nieuwenhuizen <janneke@gnu.org> skribis:
>
>>> Am Tue, Dec 03, 2024 at 02:34:10PM +0100 schrieb Janneke Nieuwenhuizen:
>>>> * etc/teams.scm (hurd): New team.
>>>
>>> I think you should simply push these two patches :)
>>
>> Pushed as 38bbed33a28524c26ca794117f6dfed1529e2807, thanks.
>
> Thanks!  I support this new team and will add my name.  :-)

Yay, welcome!  :-)

The focus of the efforts of the hurd-team has currently shifted to
`core-package-team' ---the gcc-14 transition--- that is a prerequisite
for offloading to a 64bit hurd.

Other than that, we'll also need the hurd-vm-service-type to learn about
64bit childhurds, use qemu-7 --machine q35, teach the build farm about
hurd64, to name a few things.

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com


      reply	other threads:[~2024-12-15  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 13:34 [PATCH 1/2] teams: Add hurd team Janneke Nieuwenhuizen
2024-12-03 13:34 ` [PATCH 2/2] etc: teams: Add entry for Janneke Nieuwenhuizen Janneke Nieuwenhuizen
2024-12-03 13:46 ` [PATCH 1/2] teams: Add hurd team Andreas Enge
2024-12-03 13:53   ` Janneke Nieuwenhuizen
2024-12-14 23:53     ` Ludovic Courtès
2024-12-15  7:59       ` Janneke Nieuwenhuizen [this message]

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=875xnlfkb7.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).