From: Jeff Layton <jlayton@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, zippel@linux-m68k.org,
dhowells@redhat.com, linux-cifs-client@lists.samba.org,
codalist@TELEMANN.coda.cs.cmu.edu, joel.becker@oracle.com,
linux-ext4@vger.kernel.org, fuse-devel@lists.sourceforge.net,
cluster-devel@redhat.com,
user-mode-linux-user@lists.sourceforge.net,
mikulas@artax.karlin.mff.cuni.cz, wli@holomorphy.com,
jffs-dev@axis.com, jfs-discussion@lists.sourceforge.net,
ocfs2-devel@oss.oracle.com, reiserfs-devel@vger.kernel.org,
bfennema@falcon.csc.calpoly.edu, xfs@oss.sgi.com
Subject: Re: [PATCH 00/25] move handling of setuid/gid bits from VFS into individual setattr functions (RESEND)
Date: Tue, 7 Aug 2007 18:13:49 -0400 [thread overview]
Message-ID: <20070807181349.5d4175c7.jlayton@redhat.com> (raw)
In-Reply-To: <20070807204909.GA30159@infradead.org>
On Tue, 7 Aug 2007 21:49:09 +0100
Christoph Hellwig <hch@infradead.org> wrote:
> First thanks a lot for doing this work, it's been long needed.
>
> Second please don't send out that many patches. We encourage people
> to split things into small patches when the changes are logially
> separated. Which these are not - it's a flag day change (which btw
> is fine despite the rants soe people spewed in reply to this), so it
> should be one single patch. (Or one for all mainline filesystems +
> one per fs only in -mm to make Andrew's life a little easier if you
> really care.)
Thanks. I debated about how best to split these up. A coworker
mentioned that Andrew had tossed him back a single patch that
touched several mainline filesystems and asked him to break it
up. I took that to mean that the patches should generally be split
out, but I guess I took that too far ;-)
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2007-08-07 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 13:54 [PATCH 00/25] move handling of setuid/gid bits from VFS into individual setattr functions (RESEND) Jeff Layton
2007-08-07 20:49 ` Christoph Hellwig
2007-08-07 22:13 ` Jeff Layton [this message]
2007-08-08 0:15 ` Andrew Morton
2007-08-08 0:45 ` Trond Myklebust
2007-08-08 0:54 ` Andrew Morton
2007-08-10 20:47 ` Jeff Layton
2007-08-11 2:57 ` Christoph Hellwig
2007-08-13 12:01 ` Jeff Layton
2007-08-13 12:36 ` Jeff Layton
2007-08-08 5:14 ` [fuse-devel] " Miklos Szeredi
2007-08-08 12:54 ` Jeff Layton
2007-08-08 16:48 ` Andrew Morton
2007-08-08 20:05 ` [fuse-devel] " Jan Engelhardt
2007-08-09 11:55 ` Jeff Layton
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=20070807181349.5d4175c7.jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=cluster-devel@redhat.com \
--cc=codalist@TELEMANN.coda.cs.cmu.edu \
--cc=dhowells@redhat.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=jffs-dev@axis.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=joel.becker@oracle.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=ocfs2-devel@oss.oracle.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=wli@holomorphy.com \
--cc=xfs@oss.sgi.com \
--cc=zippel@linux-m68k.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