From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Multi Cluster Power Management infrastructure
Date: Sun, 7 Apr 2013 01:32:39 +0100 [thread overview]
Message-ID: <20130407003239.GA25225@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130407002342.GJ17995@n2100.arm.linux.org.uk>
On Sun, Apr 07, 2013 at 01:23:42AM +0100, Russell King - ARM Linux wrote:
> On Fri, Apr 05, 2013 at 09:30:58AM -0400, Nicolas Pitre wrote:
> > > Now, I'm currently on holiday. I'm going to be on holday until after
> > > mid-April. I'm not pulling anything until then. I'm not applying anything
> > > until then. I'm not even reading this mailbox - and given current mail
> > > rates at 300-400 messages per day, I will *not* be reading back over a
> > > fortnights worth of email.
> >
> > That is also unacceptable. Again, you are the appointed ARM kernel
> > maintainer. You have to plan a backup when you are away. If the load
> > is too much, you have to delegate.
>
> Thank you for showing what a self-centred individual you are.
>
> Tell me, how do I delegate the physical act of scanning through email
> to someone else to find out those emails which I may want to reply to?
>
> Now, just take a moment to do the math. At 400 messages per day, with
> an average of one minute a message, that's 6.5 hours. Four days of that
> and you're looking at 20 hours to catch up - realistically two days.
> Meanwhile another 13 hours of messages (800) have arrived. So that's
> another day and a bit of nothing but scanning, during which time more
> than 6.5 hours of messages have again arrived...
>
> I've said this before, and I've done the above before - over a much
> longer period. Other kernel developers do this too - they will actively
> remove their mailboxes after returning from a vacation because its
> too painful to catch up by reading mail. Linus will also do the same -
> he will require things to be (re-)sent when he's returned from vacation.
>
> Yet _you_ seem to think that this is not acceptable behaviour? Sorry,
> I disagree - it's the _only_ sensible and sane way.
And the last thing to mentoion is that this is the last night before I
drive back home, and I've just spent the last *two* hours dealing with your
crap emails. It's now 1:30am. If I have an accident as a result of
this lack of sleep then I hold you responsible for it, because obviously
your patches are far more important than anything else in the whole damned
world.
next prev parent reply other threads:[~2013-04-07 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 16:41 [GIT PULL] Multi Cluster Power Management infrastructure Nicolas Pitre
2013-03-28 13:48 ` Lorenzo Pieralisi
2013-04-03 3:00 ` Nicolas Pitre
2013-04-05 2:03 ` Nicolas Pitre
2013-04-05 9:41 ` Russell King - ARM Linux
2013-04-05 13:30 ` Nicolas Pitre
2013-04-07 0:23 ` Russell King - ARM Linux
2013-04-07 0:32 ` Russell King - ARM Linux [this message]
2013-04-05 20:33 ` Arnd Bergmann
2013-04-05 21:07 ` Olof Johansson
2013-04-05 21:32 ` Nicolas Pitre
2013-04-06 17:46 ` Grant Likely
2013-04-07 0:02 ` Russell King - ARM Linux
2013-04-09 5:20 ` Nicolas Pitre
-- strict thread matches above, loose matches on Subject: below --
2013-02-06 19:12 Nicolas Pitre
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=20130407003239.GA25225@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).