public inbox for gentoo-ppc-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kevin Geiss <kevin@desertsol.com>
Cc: gentoo-ppc-dev@gentoo.org
Subject: Re: [gentoo-ppc-dev] Automated keyword generation
Date: Tue, 2 Dec 2003 20:51:46 -0700	[thread overview]
Message-ID: <042642C1-2544-11D8-98C3-000393C3A252@desertsol.com> (raw)
In-Reply-To: <200312021501.42188.wesm@libretech.org>

I think it's a cool idea. :)

On Tuesday, December 2, 2003, at 03:01  PM, Wes Morgan wrote:
> Has anyone ever considered/implemented an automated build success 
> report
> system? So that if I, for instance, successfully merged an ebuild w/ 
> no ppc
> or ~ppc keyword, this utility could phone home and record my success. 
> Then
> maybe that could automatically mark that package with a ~ppc keyword, 
> then if
> enough success reports came in while it was marked ~ppc (and maybe it 
> could
> be balanced against failure reports), it could automatically get 
> marked ppc
> one day.


--
gentoo-ppc-dev@gentoo.org mailing list


  reply	other threads:[~2003-12-03  3:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 22:01 [gentoo-ppc-dev] Automated keyword generation Wes Morgan
2003-12-03  3:51 ` Kevin Geiss [this message]
2003-12-03  4:02 ` Lloyd D Budd
2003-12-03  4:14 ` Marc Ozon

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=042642C1-2544-11D8-98C3-000393C3A252@desertsol.com \
    --to=kevin@desertsol.com \
    --cc=gentoo-ppc-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