From: Rusty Russell <rusty@rustcorp.com.au>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
Benny Halevy <bhalevy@panasas.com>, Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, Andy Adamson <andros@netapp.com>,
Fredric Isaman <iisaman@citi.umich.edu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alexander Beregalov <a.beregalov@gmail.com>,
Subrata Modak <subrata@linux.vnet.ibm.com>,
sachinp <sachinp@linux.vnet.ibm.com>
Subject: Re: [PATCH -next] lib: Move find_last_bit.o to obj-y to enable use by modules.
Date: Sun, 26 Apr 2009 22:19:05 +0930 [thread overview]
Message-ID: <200904262219.07148.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1240504730.11148.13.camel@heimdal.trondhjem.org>
On Fri, 24 Apr 2009 02:08:50 am Trond Myklebust wrote:
> > > On Thu, 2009-04-23 at 22:25 +0900, Paul Mundt wrote:
> > > > > In any case, this patch does not belong in the NFS tree since it touches
> > > > > generic library code, not NFS code. Benny, if nobody else wants to
> > > > > shepherd it, then just send it directly to Linus.
...
> > The nfs tree should be dropped on the floor immediately until this issue
> > is resolved.
>
> Whatever...
FWIW Trond, I would have taken the patch and pushed it. It happens: it's
not your fault, but it suddenly became your problem.
And Paul: being right doesn't excuse being an asshole.[1]
Thanks,
Rusty.
[1] As this rule applies to this message, I ponder my own failings.
next prev parent reply other threads:[~2009-04-26 12:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 3:07 [PATCH -next] lib: Move find_last_bit.o to obj-y to enable use by modules Paul Mundt
2009-04-16 8:11 ` Benny Halevy
2009-04-23 6:50 ` Paul Mundt
2009-04-23 10:12 ` Benny Halevy
2009-04-23 10:29 ` Paul Mundt
2009-04-23 12:59 ` Trond Myklebust
2009-04-23 13:18 ` Benny Halevy
2009-04-23 13:25 ` Paul Mundt
2009-04-23 13:59 ` Trond Myklebust
2009-04-23 14:12 ` Paul Mundt
2009-04-23 16:38 ` Trond Myklebust
2009-04-26 12:49 ` Rusty Russell [this message]
2009-04-26 16:42 ` Ingo Molnar
2009-04-26 17:29 ` Trond Myklebust
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=200904262219.07148.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=Trond.Myklebust@netapp.com \
--cc=a.beregalov@gmail.com \
--cc=andros@netapp.com \
--cc=bhalevy@panasas.com \
--cc=iisaman@citi.umich.edu \
--cc=lethal@linux-sh.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.com \
/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).