public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfs: rename "linux-2.6" subdirectory to be simply "linux"
Date: Fri, 22 Jul 2011 10:34:20 -0400	[thread overview]
Message-ID: <20110722143420.GE19681@infradead.org> (raw)
In-Reply-To: <201107211804.p6LI4Rvf006075@stout.americas.sgi.com>

On Thu, Jul 21, 2011 at 01:04:26PM -0500, Alex Elder wrote:
> Rename the "linux-2.6" platform-specific subdirectory in XFS to just
> be "linux".  This is consistent with the "new" Linux development
> model (regular stable releases rather than the old even/odd cycle
> with long periods between stable releases).  It was also inspired by
> Linus' recent rename of top-level git repository for the Linux code.

Actually it should just go away.  It's a leftover from when we had
code for Linux 2.4 and Linux 2.6 in the same ptools repository.

I was going to suggest near the end of the merge window that we'll
simply apply a big git rename to kill all the subdirectories which
create nothing but pain.  Now that the modular quota options (which
never made it to mainline anyway) is gone there's absolutely no need
for the quota directly, and support/ only has the uuid helpers left,
which are about to get mostly replaced by common code anyway.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-07-22 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 18:04 [PATCH, RFC] xfs: rename "linux-2.6" subdirectory to be simply "linux" Alex Elder
2011-07-22 14:34 ` Christoph Hellwig [this message]
2011-07-22 14:53   ` Alex Elder
2011-07-22 14:58     ` Christoph Hellwig

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=20110722143420.GE19681@infradead.org \
    --to=hch@infradead.org \
    --cc=aelder@sgi.com \
    --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