From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] On the usefulness of eclass changelog
Date: Wed, 31 Oct 2012 14:17:30 -0400 [thread overview]
Message-ID: <CAGfcS_kvDGeDeeKjn7HLgKO3odMF6d_biCqeTAqrye=SYfvKLg@mail.gmail.com> (raw)
In-Reply-To: <50914EB8.60501@gentoo.org>
On Wed, Oct 31, 2012 at 12:15 PM, Samuli Suominen <ssuominen@gentoo.org> wrote:
> eclass/ handling should go to repoman and the automated ChangeLog process,
> should be rather straight forward for knowing person.
Perhaps, but right now the policy is to update it, so do it. The
policy is also to post eclass changes for review on -dev, so do that
too. That means do it BEFORE you commit it. I don't care if you post
it raw, or post a link to a file, or post a link to a proposed commit
on your private little git branch, but don't commit it and then send
out a link to the commit in production after the fact.
This whole double-thread is ridiculous. If somebody at work
deliberately violated a dumb policy and pointed out it was dumb, the
answer would be, "thanks, we'll look into changing the dumb policy,
now pack up your desk to make room for the new employee who can
benefit from the improved policy."
If you don't like the rules feel free to whine, beg, and plead to QA,
the council, $DIETY, or your mother, but follow the rules until
they're changed. There is always room for mistakes, but big projects
don't work when everybody just does whatever they feel like doing.
Rich
next prev parent reply other threads:[~2012-10-31 18:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121030190839.A9A3D21600@flycatcher.gentoo.org>
2012-10-30 19:17 ` [gentoo-dev] Re: gentoo-x86/eclass: udev.eclass Fabian Groffen
2012-10-30 19:31 ` Samuli Suominen
2012-10-30 19:49 ` Samuli Suominen
2012-10-30 20:47 ` Doug Goldstein
2012-10-30 21:16 ` Fabian Groffen
2012-10-30 21:22 ` Samuli Suominen
2012-10-31 7:50 ` Fabian Groffen
2012-10-31 7:51 ` Samuli Suominen
2012-10-31 8:56 ` Fabian Groffen
2012-10-31 16:08 ` Samuli Suominen
2012-10-31 16:21 ` Gilles Dartiguelongue
2012-10-31 16:55 ` Samuli Suominen
2012-10-31 15:04 ` Alexis Ballier
2012-10-31 16:19 ` Samuli Suominen
2012-10-30 22:04 ` Ciaran McCreesh
2012-10-30 21:24 ` Michał Górny
2012-10-30 21:28 ` Samuli Suominen
2012-10-31 0:39 ` Ryan Hill
2012-10-31 15:26 ` [gentoo-dev] On the usefulness of eclass changelog Alexis Ballier
2012-10-31 15:35 ` Ian Stakenvicius
2012-10-31 15:39 ` Alexis Ballier
2012-10-31 16:15 ` Samuli Suominen
2012-10-31 16:26 ` Ian Stakenvicius
2012-10-31 16:38 ` Alexis Ballier
2012-10-31 16:45 ` Jeroen Roovers
2012-10-31 18:17 ` Rich Freeman [this message]
2012-10-31 18:33 ` Samuli Suominen
2012-10-30 19:56 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: udev.eclass Alexis Ballier
2012-10-30 19:57 ` Samuli Suominen
2012-10-30 20:08 ` Alexis Ballier
2012-10-30 20:18 ` Michał Górny
2012-10-30 20:19 ` Samuli Suominen
2012-10-31 14:57 ` Alexis Ballier
2012-10-31 15:09 ` Michał Górny
2012-10-31 15:36 ` Samuli Suominen
2012-10-31 19:17 ` Markos Chandras
2012-10-30 20:06 ` Fabian Groffen
2012-10-30 20:06 ` Ian Stakenvicius
2012-10-30 20:08 ` Samuli Suominen
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='CAGfcS_kvDGeDeeKjn7HLgKO3odMF6d_biCqeTAqrye=SYfvKLg@mail.gmail.com' \
--to=rich0@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