From: Alex Elder <aelder@sgi.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <xfs@oss.sgi.com>,
<akpm@linux-foundation.org>
Subject: Re: [GIT PULL] XFS update for 3.1-rc4
Date: Tue, 23 Aug 2011 14:57:56 -0500 [thread overview]
Message-ID: <1314129476.2898.28.camel@doink> (raw)
In-Reply-To: <CA+55aFxEyj8qJnr9QR3Scy7SFocEr2BNA9z4PXs7q9rpkXM1vQ@mail.gmail.com>
On Tue, 2011-08-23 at 11:46 -0700, Linus Torvalds wrote:
> On Tue, Aug 23, 2011 at 10:39 AM, Alex Elder <aelder@sgi.com> wrote:
> >
> > Linus, please pull the following XFS changes. Their effect is to
> > remove the subdirectory structure from the XFS source hierarchy.
> > There are no functional changes to the XFS code itself. Thanks.
>
> Pulled.
>
> Any plans to further sanitize the namespace?
We haven't discussed it but it's not a bad idea.
> It's kind of crazy to have filenames like
>
> fs/xfs/xfs_trace.c
>
> which just duplicate the "xfs" part for no good reason. Why not just
> do something like
>
> for i in xfs_*; do j=$(echo $i | sed 's/^xfs_//'); git mv $i $j; done
>
> to get rid of the silly "xfs_" prefix that adds nothing?
>
> You could use the bytes you save to rename "qm.c" to "quota_manager.c"
> instead. Wouldn't it be nice to have *good* names, instead of a jumble
> of crazy and mostly redundant letters?
We're getting there, gradually. The code is certainly
evolving in that direction, though that hasn't happened
in the file names. Doing that would require my fingers
to get used to skipping over the "xfs_" spasm though...
-Alex
next prev parent reply other threads:[~2011-08-23 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 17:39 [GIT PULL] XFS update for 3.1-rc4 Alex Elder
2011-08-23 18:46 ` Linus Torvalds
2011-08-23 19:57 ` Alex Elder [this message]
2011-08-24 0:42 ` Dave Chinner
2011-08-24 0:59 ` Linus Torvalds
2011-08-24 7:42 ` Dave Chinner
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=1314129476.2898.28.camel@doink \
--to=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.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