Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] nfs-utils:  Support binding to source address.
Date: Thu, 09 Jun 2011 17:16:50 -0400	[thread overview]
Message-ID: <4DF13842.1020307@RedHat.com> (raw)
In-Reply-To: <4DF102E0.5000201@candelatech.com>



On 06/09/2011 01:29 PM, Ben Greear wrote:
> On 06/09/2011 10:18 AM, Steve Dickson wrote:
>> Hello,
>>
>>
>> On 06/08/2011 07:01 PM, greearb@candelatech.com wrote:
>>> From: Ben Greear<greearb@candelatech.com>
>>>
>>> This lets one specify the source IP address for
>>> sockets, allowing users to leverage routing rules
>>> on multi-homed systems.
>> Right out of the box I do think some support like
>> this would be good... but I not convinced on how needed
>> something like this is which means there is a lot of
>> change here for basically not... But lets continue
>> to talk about to see where we end up....
>>
>> One thing you must do is break up this patch in to
>> a more readable patch series. There is no way I going
>> to commit a patch that is close to 1500 lines
>> that so invasive.
> 
> The vast majority of the patch is adding an extra
> argument to various methods to get things to compile.
Yeah I know... I saw that... But there has to be
some logical way to break this up.. 

> 
> Do you want me to break those changes into individual
> chunks, or should I just separate the parsing & documentation
> chunks out?
I guess that would be start.... but just breaking this up
unto just a couple patches probably will not do anything for
readability either... 
 
> 
> I can dummy stuff out with passing NULL around to make
> lots of smaller patches, but I'm not sure it helps
> any readability.
I don't know either... but it make me very nervous 
to apply a 1400+ line patch especially when its basically
rewriting mount... I've broken mount before... Its not
a pretty sight... ;-)

steved.  
> 
> Thanks,
> Ben
> 
> 

  reply	other threads:[~2011-06-09 21:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 23:01 [PATCH v2] nfs-utils: Support binding to source address greearb
2011-06-09 14:05 ` Chuck Lever
2011-06-09 15:50   ` Ben Greear
2011-06-09 18:39     ` Chuck Lever
2011-06-09 23:47       ` Ben Greear
2011-06-09 17:18 ` Steve Dickson
2011-06-09 17:29   ` Ben Greear
2011-06-09 21:16     ` Steve Dickson [this message]
2011-06-09 21:25       ` Ben Greear
2011-06-09 23:48         ` Ben Greear

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=4DF13842.1020307@RedHat.com \
    --to=steved@redhat.com \
    --cc=greearb@candelatech.com \
    --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