From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ruby keywording
Date: Wed, 07 Mar 2012 19:56:53 +0100 [thread overview]
Message-ID: <1331146613.21630.11.camel@graaff.xs4all.nl> (raw)
In-Reply-To: <4F570780.2030409@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
On Wed, 2012-03-07 at 08:00 +0100, "Paweł Hajdan, Jr." wrote:
> It's trivial to set up x86 chroot on amd64 box, so I can't imagine
> what's preventing people from creating such chroot, doing the testing
> and keywording themselves.
In my personal case what is preventing me is sheer and utter
disinterest. For me x86 and, say, sh, are similar arches. I'm happy to
support both via keywording and stabilization bugs, but I'd rather spent
what little time I have these days on actual ruby stuff.
Kind regards,
Hans
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2012-03-07 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 22:17 [gentoo-dev] Ruby keywording Thomas Kahle
2012-03-06 22:42 ` Jeroen Roovers
2012-03-07 7:00 ` "Paweł Hajdan, Jr."
2012-03-07 12:25 ` Alexis Ballier
2012-03-07 14:54 ` Thomas Kahle
2012-03-07 16:09 ` Alexis Ballier
2012-03-07 18:56 ` Hans de Graaff [this message]
2012-03-07 18:52 ` Hans de Graaff
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=1331146613.21630.11.camel@graaff.xs4all.nl \
--to=graaff@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