From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: udev.eclass
Date: Wed, 31 Oct 2012 17:36:10 +0200 [thread overview]
Message-ID: <5091456A.4030307@gentoo.org> (raw)
In-Reply-To: <20121031160909.674d542a@pomiocik.lan>
On 31/10/12 17:09, Michał Górny wrote:
> On Wed, 31 Oct 2012 11:57:49 -0300
> Alexis Ballier <aballier@gentoo.org> wrote:
>
>> On Tue, 30 Oct 2012 21:18:02 +0100
>> Michał Górny <mgorny@gentoo.org> wrote:
>> [...]
>>> Don't even try to touch any of my eclasses without prior asking.
>>
>> A bit aggressive but its rather obvious that this is the norm not the
>> exception, meaning the argument 'I do not want to diverge from
>> $other eclass' is moot.
>
> It's aggressive because Samuli has a history of touching (and sometimes
> breaking) other people's packages without even asking or pinging that
> he did that, and believing he's above all the rules here.
>
You don't know me clearly, that's definately the opposite of what I'm
doing and intending to do, walking the fine line and bothering people
only when something real changes...
Breaking? Hardly, since I never commit untested code, and the exceptions
I've fixed myself usually very quickly as I'm watching incoming bugs,
forums, and more
I'm being cooperative with you and keeping udev.eclass with
systemd.eclass sort of 'in sync' due to the nature of both
packages being from the same tarball. What more do you want? Seriously.
next prev parent reply other threads:[~2012-10-31 15:42 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
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 [this message]
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=5091456A.4030307@gentoo.org \
--to=ssuominen@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