From: Linus Torvalds <torvalds@linux-foundation.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dhowells@redhat.com
Subject: Re: [GIT PULL] Please pull the first batch of NFS client changes (and cachefs merge)...
Date: Wed, 1 Apr 2009 09:43:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904010935000.4130@localhost.localdomain> (raw)
In-Reply-To: <1238522824.6577.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Tue, 31 Mar 2009, Trond Myklebust wrote:
>
> Please pull from the "for-linus" branch of the repository at
>
> git pull git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git for-linus
I _really_ want fscache to come with way more Acked-by's etc.
So no, I'm not going to pull this. I want a lot more than just
Signed-off-by: David Howells <dhowells@redhat.com>
on the 100+ lines of changes to the VM. I want the VM people pinged and
asked whether it's ok.
And I also have a stupid trivial complaint:
WTF is up with absolutely inane crap like this:
> fs/cachefiles/cf-bind.c | 286 +++++++
> fs/cachefiles/cf-daemon.c | 754 ++++++++++++++++++
> fs/cachefiles/cf-interface.c | 449 +++++++++++
> fs/cachefiles/cf-internal.h | 360 +++++++++
> fs/cachefiles/cf-key.c | 159 ++++
> fs/cachefiles/cf-main.c | 106 +++
> fs/cachefiles/cf-namei.c | 772 +++++++++++++++++++
> fs/cachefiles/cf-proc.c | 134 ++++
> fs/cachefiles/cf-rdwr.c | 853 +++++++++++++++++++++
> fs/cachefiles/cf-security.c | 116 +++
> fs/cachefiles/cf-xattr.c | 291 +++++++
...
> fs/fscache/fsc-cache.c | 415 ++++++++++
> fs/fscache/fsc-cookie.c | 498 ++++++++++++
> fs/fscache/fsc-fsdef.c | 144 ++++
> fs/fscache/fsc-histogram.c | 109 +++
> fs/fscache/fsc-internal.h | 380 +++++++++
> fs/fscache/fsc-main.c | 124 +++
> fs/fscache/fsc-netfs.c | 103 +++
> fs/fscache/fsc-object.c | 810 +++++++++++++++++++
> fs/fscache/fsc-operation.c | 459 +++++++++++
> fs/fscache/fsc-page.c | 771 +++++++++++++++++++
> fs/fscache/fsc-proc.c | 68 ++
> fs/fscache/fsc-stats.c | 212 +++++
What the hell is that "cf-" and "fsc-" prefix? We don't do single-level
naming crud. It's already in a directory hierarchy, why the _hell_ does it
then add some idiotic extra prefix that is just a (very inferior) copy of
that hierarchy?
If you want to write "fscache", write it out. Don't do "fsc". And do it as
a directory. But then even an idiot would see that calling it
fs/fscache/fscache/proc.c is a bit redundant. So why do you call it
fs/fscache/fsc-proc.c?
Gaah. Naming is a bid deal for me, and the above is just crap.
Linus
next prev parent reply other threads:[~2009-04-01 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 18:07 [GIT PULL] Please pull the first batch of NFS client changes (and cachefs merge) Trond Myklebust
[not found] ` <1238522824.6577.5.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-01 16:43 ` Linus Torvalds [this message]
[not found] ` <alpine.LFD.2.00.0904010935000.4130-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-04-01 17:24 ` David Howells
2009-04-02 4:33 ` Miles Bader
[not found] ` <1526.1238664007@redhat.com>
2009-04-02 18:56 ` Miles Bader
2009-04-01 17:31 ` 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=alpine.LFD.2.00.0904010935000.4130@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=Trond.Myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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).