From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linuxt-next: nfsd strange commit
Date: Tue, 21 Oct 2008 09:20:59 -0400 [thread overview]
Message-ID: <20081021132059.GA8029@fieldses.org> (raw)
In-Reply-To: <20081021141357.ab15406f.sfr@canb.auug.org.au>
On Tue, Oct 21, 2008 at 02:13:57PM +1100, Stephen Rothwell wrote:
> Hi Bruce,
>
> I was just wondering what commit 9966acbedc54b9c2d38d97bdd56b612d8da45b8d
> ("proc: move rest of /proc/locks to fs/locks.c") is doing in the
> nfsd-next tree? As far as I can see, it has nothing to do with nfsd and
> no interaction with the nfsd code.
>
> Adding random patches to trees in linux-next just makes my job
> harder ... especially when it touched something like include/linux/fs.h
> and triggers a major rebuild of the tree (*and* it is the only thing in
> the nfsd-next tree).
I've also been acting as a (somewhat inconsistent) locks.c maintainer.
Would it make it any easier if I kept a locks-next branch that you could
pull separately? Or should I try to get that stuff into some other
tree?
--b.
next prev parent reply other threads:[~2008-10-21 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 3:13 linuxt-next: nfsd strange commit Stephen Rothwell
2008-10-21 13:20 ` J. Bruce Fields [this message]
2008-10-22 22:30 ` Stephen Rothwell
2008-10-23 2:55 ` J. Bruce Fields
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=20081021132059.GA8029@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.