From: Alistair Bush <ali_bush@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] QA: java-experimental
Date: Mon, 02 Feb 2009 00:03:44 +1300 [thread overview]
Message-ID: <49858190.10505@gentoo.org> (raw)
In-Reply-To: <49857A41.7060409@gentoo.org>
Krzysztof Pawlik wrote:
> I've fixed few packages, and... leesten carefully... I'm going to say
this only
> once: next person to commit an ebuild with KEYWORDS="" (or KEYWORDS="-*") will
> be punished... Alistair will send an e-mail every 10 minutes until the ebuild
> gets proper keywords and ends up in package.mask.
>
Oh shit
/me runs back to reverse all the commits in which I dropped all
keywords. ;)
On a more serious note.
KEYWORDS="-*" is bad!!! and if I see anymore of it an email every 10
minutes will be the last of anyones problems.
but im not that concerned about KEYWORDS=""
I dropped keywords on a few packages in java-overlay because there deps
weren't satisfied within gentoo or java-overlay ( I didn't check
java-experimental unless it was obvious to me. aka hibernate-annotations
). Eventually there will be an email going around with a list of ebuilds
that have no keywords. These will either be junkyarded or moved to
java-experimental (if that satisfies them).
> Can we get commit hook that does some basic QA and aborts the commit if there
> are QA errors (and some warning)?
I will look into this at some point. I suppose there are many things we
could do to help maintain qa. I suppose we also need more overview of
our contributors. So I might attempt to generate reports, etc of
commits by those users.
next prev parent reply other threads:[~2009-02-01 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 2:11 [gentoo-java] QA: java-experimental Alistair Bush
2009-02-01 10:32 ` Krzysztof Pawlik
2009-02-01 11:03 ` Alistair Bush [this message]
2009-02-01 11:31 ` Krzysztof Pawlik
2009-02-01 18:33 ` Alistair Bush
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=49858190.10505@gentoo.org \
--to=ali_bush@gentoo.org \
--cc=gentoo-java@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