From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: x86@gentoo.org, ppc@gentoo.org, ia64@gentoo.org,
alpha@gentoo.org, sparc@gentoo.org
Subject: [gentoo-dev] Hey arch teams, we need your input!
Date: Sat, 11 Apr 2015 21:50:13 +0200 [thread overview]
Message-ID: <201504112150.13880.dilfridge@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi all,
the debate about arches, keywording and stabilization procedures is coming up again.
People have told me that the whole debate seems to turn into some sort of arch-team bashing. That is definitely not the plan. Also, supporting many different types of hardware is actually one of the strong points of Gentoo.
So, it would be absolutely great to have more feedback from the arch teams, especially suggestions
* how to improve procedures,
* where you see the main problems, and
* where you don't see problems...
Please make your voice heard. Noone wants to overrule an active team.
Cheers,
Andreas
PS. I've ommitted amd64, hppa, and arm from the manual CC list because these are the stable arches I'm definitely not worried about. Obviously feedback is appreciated anyway.
- --
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0
iQJ8BAEBCgBmBQJVKXr1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0RkJDMzI0NjNBOTIwMDY5MTQ2NkMzNDBF
MTM4NkZEN0VGNEI1Nzc5AAoJEOE4b9fvS1d5eOgP/i6kqnWoUEy2NiI8OcD9qGr6
cvkm1g/nx02r5GRickqPhUrZNbjvG7qeG5E0e00szNwTG8whV3e1jKd90bmHhw2S
ZqKDUd0pJHmGk/otpPq3rTZXUAtw0eOF6Y3J86DChlaHtyug2hk5/EU7tKgIXDKp
hpuMvU4hs2+IAYr4ML0LXY7LFE4RT0ZxxZ62p7AtwR/9CCa9m8rtgd4/BVqUkol2
SgMRAEpBIeI72KO8aYPt8I0S83XuI5fL/zMaOhlLwkx5ioVeC+HkgcN4n3uEPW71
MoYy5JQjkX9DDWTd7HWot33NC/WCl8D+v3wprlcQC6a2iKgQdl7fbPanuJUKr//w
EuEYxQab9XV9TchhkJ+tKR7V2PiW9pCGDJJSlQcAjppY9LMza2UNMJLa61dnNpkp
r0EtLi6uyyoV3sCuI+lOvaG3e3o8RGFrQ/PGn/MJtIx7q0j72f7yuLz3jz4Da+yR
CKRzzAz71cjqpkHogY5mxdNeAtG/Lsa/9Qt4E4+i2B/AqDeRLSR6nuc73lPonR16
ScVpIsyd43Ta5NL4arL4WuN951ngmqDc6R4ISnt/dTs+yHVfhL9/P2E5YFCu0ydl
O8tb40f1A8Pb8MpDVy06w52bwI6FNGtcQVL511xxaubbK/zrJq+xKgOSd+u1B6lp
zPx2On+Fnysyhg8COUuo
=4wlA
-----END PGP SIGNATURE-----
next reply other threads:[~2015-04-11 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 19:50 Andreas K. Huettel [this message]
2015-04-11 20:51 ` [gentoo-dev] Hey arch teams, we need your input! Pacho Ramos
2015-04-11 21:08 ` Mikle Kolyada
2015-04-26 9:59 ` Pacho Ramos
2015-04-26 12:04 ` Rich Freeman
2015-04-26 12:12 ` Pacho Ramos
2015-04-26 16:20 ` Jeroen Roovers
2015-04-28 9:07 ` Tobias Klausmann
2015-05-15 8:51 ` Pacho Ramos
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=201504112150.13880.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--cc=alpha@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ia64@gentoo.org \
--cc=ppc@gentoo.org \
--cc=sparc@gentoo.org \
--cc=x86@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