From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Bryan Schumaker <bjschuma@netapp.com>,
trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [RFC 0/4] NFS: Modularize NFS v3
Date: Fri, 2 Dec 2011 11:24:31 -0500 [thread overview]
Message-ID: <20111202162431.GC14393@fieldses.org> (raw)
In-Reply-To: <4ED8318B.5040400@RedHat.com>
On Thu, Dec 01, 2011 at 09:01:47PM -0500, Steve Dickson wrote:
>
>
> On 12/01/2011 04:55 PM, Bryan Schumaker wrote:
> > On Thu Dec 1 16:05:03 2011, Steve Dickson wrote:
> >> Now what is the motivating reason behind this re-architecture
> >> other than making the upstream kernel literally impossible to
> >> back port to older kernels??
> >>
> > I wasn't thinking about backporting when I did this... is there a
> > better way to do this that wouldn't make it a pain to backport?
> Yeah... Don't do it! 8-) Major architectural changes always destroy
> any all chances of clean back ports... That's why they are generally
> done on major releases... the when 3.X was released...
There was nothing special about 3.0 other than the name; it could just
as easily have been called 2.6.40.
But anyway I don't see the big problem for backports. Probably git can
deal with the renames automatically, and even if it can't the fixup is
going to be pretty obvious. This isn't like the xdr changes that
touched so many lines, it's mainly just a simple rename.
--b.
next prev parent reply other threads:[~2011-12-02 16:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 16:48 [RFC 0/4] NFS: Modularize NFS v3 bjschuma
2011-12-01 16:48 ` [RFC v2 1/4] NFS: Export symbols needed by an NFS v3 module bjschuma
2011-12-01 16:48 ` [RFC v2 2/4] NFS: Move the NFS v3 code into its own subdirectory bjschuma
2011-12-01 16:48 ` [RFC v2 3/4] NFS: Add functions for adding new NFS versions bjschuma
2011-12-01 16:48 ` [RFC v2 4/4] NFS: Turn NFS v3 into a module bjschuma
2011-12-01 17:36 ` [RFC 0/4] NFS: Modularize NFS v3 Jim Rees
2011-12-01 19:56 ` Bryan Schumaker
2011-12-01 21:05 ` Steve Dickson
2011-12-01 21:55 ` Bryan Schumaker
2011-12-01 21:57 ` Trond Myklebust
2011-12-02 2:38 ` Steve Dickson
2011-12-02 2:01 ` Steve Dickson
2011-12-02 16:24 ` J. Bruce Fields [this message]
2012-01-10 17:42 ` Stanislav Kinsbursky
2012-01-10 17:58 ` Bryan Schumaker
-- strict thread matches above, loose matches on Subject: below --
2011-11-22 22:57 bjschuma
2011-11-23 2:19 ` Boaz Harrosh
2011-11-23 2:41 ` Jim Rees
2011-11-28 14:14 ` Bryan Schumaker
2011-11-23 18:27 ` 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=20111202162431.GC14393@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.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;
as well as URLs for NNTP newsgroup(s).