From: Peter Ruskin <aoyu93@dsl.pipex.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Testing and reporting ~x86
Date: Sun, 10 Nov 2002 14:14:03 +0000 [thread overview]
Message-ID: <200211101414.03562.aoyu93@dsl.pipex.com> (raw)
I have 3 working Gentoo systems on different partitions on my main box: 1.2,
1.4beta and "unstable" 1.4 with ACCEPT_KEYWORDS="~x86".
Is there an easy way to grep all "~x86" installed builds, so that I can report
to bugzilla those that "work for me"?
I mainly work with 'unstable' and check/report with bugzilla on those that
fail. However, with a (roughly) daily `emerge rsync` and `emerge -u world`,
it's easy to miss those that work and I can see it would be helpful to report
those.
Peter
--
Gentoo Linux 1.4 (Portage 2.0.43 (default-x86-1.4, gcc-3.2,
glibc-2.3.1-r1,2.3.1-r2)). KDE: 3.0.4 Qt: 3.0.5
AMD Athlon(tm) XP 1900+ 512MB. Kernel: 2.4.19-win4lin. GCC 3.2
Linux user #275590 (http://counter.li.org/). up 53 min.
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-11-10 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 14:14 Peter Ruskin [this message]
2002-11-12 13:53 ` [gentoo-dev] Testing and reporting ~x86 Peter Ruskin
2002-11-12 19:41 ` Peter Ruskin
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=200211101414.03562.aoyu93@dsl.pipex.com \
--to=aoyu93@dsl.pipex.com \
--cc=gentoo-dev@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