From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-dev-announce] New alias to help with cross-compilation: cross@gentoo.org
Date: Wed, 3 Oct 2018 22:15:39 +0200 [thread overview]
Message-ID: <3aace776-5c9b-3c8a-52ed-37ed47c84a2d@gentoo.org> (raw)
In-Reply-To: <1538332673.737.2.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
Hi,
> Since with EAPI 7 support for cross-compilation became something more
> official, I've created cross@ alias on woodpecker. The idea is to have
> something like prefix@ -- when people report that stuff doesn't cross
> compile right and you can't help them, you assign it to cross@ and hope
> someone would ;-).
> Also, if you'd like to help out, please add yourself to the alias.
Thank you. I just added it to the documentation on
https://wiki.gentoo.org/wiki/Project:Bug-wranglers#Assigning_bug_reports
--
Best,
Jonas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 636 bytes --]
prev parent reply other threads:[~2018-10-03 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 18:37 [gentoo-dev] New alias to help with cross-compilation: cross@gentoo.org Michał Górny
2018-10-03 20:15 ` Jonas Stein [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3aace776-5c9b-3c8a-52ed-37ed47c84a2d@gentoo.org \
--to=jstein@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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