From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: netfilter-devel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: essentially offline...
Date: Thu, 08 Nov 2012 15:09:30 -0500 (EST) [thread overview]
Message-ID: <20121108.150930.2104308040240146535.davem@davemloft.net> (raw)
Once again I am without any real internet access both at home (Time
Warner major Manhattan outage since this morning) and at the office
(Verizon still largely out in Lower Manhattan).
So I'm not going to be resonsive until one of these two outages are
resolved. I cannot even call Time Warner customer support, I get "all
circuits are busy" so they're obviously getting bombed with calls.
Want to help? There are two ways:
1) Don't do anything that makes more overhead for me.
Don't ask about patch status, that's what the heck patchwork
is for. If you're patch isn't there and active and you think
it needs to bee considered seriously, REPOST it, DON'T ASK ME
about a patch I already moved out of my TODO list. That's more
work for me.
And, this should go without saying %100 of the time, DO NOT
send me private email. It is never appropriate, I don't care
what excuse you come up with. Just simply don't do it.
2) Don't be a jackass and avoid reviewing patches that you can
actually provide feedback on.
That is what makes my backlog something that is actually
manageable, when everyone else dutifully reviews patches that get
posted so that I have something to immediately work against when I
get to reviewing that patch myself.
One great example is the gianfar patch posted the other day.
Nobody is going to review that and I know absolutely nothing
about gianfar hardware, whether that is the correct fix, etc.
So it'll either just rot there, or I'll have to guess if it's
correct.
But this is exactly what breaks down my productivity, when
people who are knowledgable don't review patches like that one.
Thanks.
next reply other threads:[~2012-11-08 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 20:09 David Miller [this message]
2012-11-08 20:53 ` essentially offline Jan Ceuleers
2012-11-08 21:01 ` David Miller
[not found] ` <20121108.160149.1435441347312920431.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-11-09 20:49 ` Jan Ceuleers
2012-11-09 22:30 ` Hannes Frederic Sowa
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=20121108.150930.2104308040240146535.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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).