From: Thomas Cort <tcort@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Security/QA Spring Cleaning
Date: Tue, 23 May 2006 22:44:15 +0000 [thread overview]
Message-ID: <20060523224415.bac5c3da.tcort@gentoo.org> (raw)
In-Reply-To: <20060523204409.GD14671@nightcrawler>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Tue, 23 May 2006 13:44:09 -0700
Brian Harring <ferringb@gmail.com> wrote:
> Couple more reports generated (in the parent dir, dropped keywords,
> imlate, packages that have just ~arch, ebuild metadata verification,
> and "ebuild has been unstable for arch X for greater then N days).
Seems like we have a lot of people generating reports....
aliz
http://gentoo.tamperd.net/stable/
blubb
http://blubb.ch/gentoo/amd64/
tcort
http://dev.gentoo.org/~tcort/imlate/
http://dev.gentoo.org/~tcort/dropped/
ferringb:
http://gentooexperimental.org/~ferringb/reports/
halcy0n:
http://dev.gentoo.org/~halcy0n/imlate/
http://dev.gentoo.org/~halcy0n/keyword-moves/
hansmi:
recently sent the output of imlate.py to amd64@g.o
Would it be possible to get a centralized place for all of this stuff?
Could a reports.gentoo.org or something similar be setup to run
scripts/programs every hour or two?
~tcort
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-05-24 2:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 3:02 [gentoo-dev] Security/QA Spring Cleaning Ned Ludd
2006-05-22 5:25 ` Robin H. Johnson
2006-05-22 5:30 ` Brian Harring
2006-05-23 20:22 ` Ned Ludd
2006-05-23 20:44 ` Brian Harring
2006-05-23 22:44 ` Thomas Cort [this message]
2006-05-23 20:51 ` Chris Gianelloni
2006-05-23 21:06 ` Brian Harring
2006-05-23 21:46 ` Chris Gianelloni
2006-05-23 22:05 ` Brian Harring
2006-05-23 22:24 ` Chris Gianelloni
2006-05-23 22:36 ` Brian Harring
2006-05-24 4:11 ` Doug Goldstein
2006-05-24 12:06 ` Chris Gianelloni
2006-05-24 12:02 ` Chris Gianelloni
2006-05-23 21:50 ` Ned Ludd
2006-05-23 22:22 ` Chris Gianelloni
2006-05-28 18:20 ` Ned Ludd
2006-05-28 20:18 ` Robin H. Johnson
2006-05-29 1:17 ` Ned Ludd
2006-05-29 20:22 ` Chris Gianelloni
2006-06-02 13:15 ` Eldad Zack
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=20060523224415.bac5c3da.tcort@gentoo.org \
--to=tcort@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