From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP concerning ebuild-development
Date: Sun, 13 Mar 2005 21:18:09 +0200 [thread overview]
Message-ID: <1110741489.24307.17.camel@nosferatu.lan> (raw)
In-Reply-To: <20050313190026.692fa5ce@snowdrop>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
On Sun, 2005-03-13 at 19:00 +0000, Ciaran McCreesh wrote:
> On Sun, 13 Mar 2005 19:49:40 +0100 Adrian Lambeck
> <adrian.lambeck@basicsedv.de> wrote:
> | Please have a look at it and tell me what you think:
> | http://www.gentoo.org/proj/en/glep/glep-0035.html
>
> Any automatic machine-done changes to ebuilds will break the tree far
> more than the occasional developer screwup.
To my shame I must concur with Ciaran ;p Maybe sending reports QA's
way, or such would be more preferred, as you can never be 100% sure that
your checking/fixing state machine is 100% correct - meaning I do think
that an human eye (which at least can contact the responsible parties)
should still be the last defence in *actually changing* ebuilds.
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-13 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 18:49 [gentoo-dev] GLEP concerning ebuild-development Adrian Lambeck
2005-03-13 19:00 ` Ciaran McCreesh
2005-03-13 19:18 ` Martin Schlemmer [this message]
2005-03-13 19:58 ` Mark Loeser
2005-03-13 21:15 ` Sami Samhuri
2005-03-13 22:22 ` Mark Loeser
2005-03-13 20:22 ` Chris Gianelloni
2005-03-13 19:27 ` Dan Armak
2005-03-13 21:05 ` Maurice van der Pot
2005-03-13 21:17 ` Ciaran McCreesh
2005-03-13 21:31 ` Lance Albertson
2005-03-13 22:08 ` Martin Schlemmer
2005-03-13 23:58 ` Lance Albertson
2005-03-14 0:29 ` Ciaran McCreesh
2005-03-14 0:40 ` Lance Albertson
2005-03-14 0:56 ` Ciaran McCreesh
2005-03-14 0:56 ` Martin Schlemmer
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=1110741489.24307.17.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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