From: Steve Dickson <SteveD@redhat.com>
To: 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 13:18:11 -0400 [thread overview]
Message-ID: <4DF10053.9050901@RedHat.com> (raw)
In-Reply-To: <1307574083-27608-1-git-send-email-greearb@candelatech.com>
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.
Here is how I create patch series.
git pull devel-tree
git checkout -b devel-branch
make changes
git commit -s -a
make more changes
git commit -s -a
[Note, each one of the commits (or patches) have to be stand-alone patches ]
[Which means after each commit the tree has to compile and be functional ]
When all the changes are done, create the patches like:
git format-patch -n -o /tmp/sumbit --cover-letter commit1^..commitN
edit /tmp/summit/*cover* to explain your changes
Then post the patches with git send-email command:
git send-email $DRYRUN --suppress-cc=all --suppress-from --no-chain-reply-to --from "Your Name <emailaddress@foobar.com>" --to Linux NFS Mailing list <linux-nfs@vger.kernel.org>" --smtp-server smtp.foobar.com /tmp/submit/*.patch
Note, I'm not sure the --smtp argument is needed... but it works..
steved.
next prev parent reply other threads:[~2011-06-09 17:18 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 [this message]
2011-06-09 17:29 ` Ben Greear
2011-06-09 21:16 ` Steve Dickson
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=4DF10053.9050901@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.