From: zimoun <zimon.toutoune@gmail.com>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 60056@debbugs.gnu.org
Subject: bug#60056: [PATCH RFC 1/6] build: Add gnu-build-system v2.
Date: Sat, 17 Dec 2022 12:53:26 +0100 [thread overview]
Message-ID: <86cz8itfex.fsf@gmail.com> (raw)
In-Reply-To: <871qp0c5g7.fsf@gmail.com>
Hi Maxim,
On Thu, 15 Dec 2022 at 23:56, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> OK. I've used the etc/teams.scm script output to CC the core team
> members. Hopefully it helped to ping them (did it for you?).
Maybe something is wrong with my config, but I am not able to find these
messages where I am CC.
Well, it is holidays in France (yeah, we have a lot ;-)) so I will not
be able to give a look before January – although, I am not convinced
that my comments would be useful.
Cheers,
simon
next prev parent reply other threads:[~2022-12-17 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 2:16 bug#60056: cross-compilation doesn't honor gcc native input Maxim Cournoyer
2022-12-15 3:23 ` bug#60056: [PATCH RFC 1/6] build: Add gnu-build-system v2 Maxim Cournoyer
2022-12-15 3:23 ` bug#60056: [PATCH RFC 2/6] build: gnu-build-system2: Remove source from native inputs Maxim Cournoyer
2022-12-15 3:23 ` bug#60056: [PATCH RFC 3/6] build-systems: gnu: Infer cross-toolchain from native-inputs components Maxim Cournoyer
2022-12-15 3:23 ` bug#60056: [PATCH RFC 4/6] gnu: glibc-2.30: Use gnu-build-system2 to fix cross-compiled build Maxim Cournoyer
2022-12-15 3:23 ` bug#60056: [PATCH RFC 5/6] gnu: make-linux-libre*: Use gnu-build-system2 to fix cross compilation Maxim Cournoyer
2022-12-15 3:23 ` bug#60056: [PATCH RFC 6/6] gnu: u-boot: Fix cross-compilation by using gnu-build-system2 Maxim Cournoyer
2022-12-15 15:09 ` bug#60056: [PATCH RFC 1/6] build: Add gnu-build-system v2 Ludovic Courtès
2022-12-16 4:56 ` Maxim Cournoyer
2022-12-17 11:53 ` zimoun [this message]
2022-12-17 15:58 ` Maxim Cournoyer
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=86cz8itfex.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=60056@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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.