From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs-utils: fix default value for --enable-tirpc
Date: Thu, 28 Oct 2010 10:03:10 -0400 [thread overview]
Message-ID: <4CC9829E.90709@RedHat.com> (raw)
In-Reply-To: <20101028093833.6541ce21@tlielax.poochiereds.net>
On 10/28/2010 09:38 AM, Jeff Layton wrote:
> On Thu, 28 Oct 2010 09:24:00 -0400
> Steve Dickson <SteveD@redhat.com> wrote:
>
>> Jeff,
>>
>> On 10/11/2010 09:29 PM, Jeff Layton wrote:
>>> The patch I originally proposed to make --enable-tirpc the default had
>>> the default for $enable_tirpc as a blank string. When it was merged
>>> however, that value was changed to a 'yes'.
>> Which commit or proposal are you talking about? I'm looking at commit 148503a
>> which changed it for no to yes, but I can not seem to find the
>> proposal you are talking about?
>>
>> I'm just trying to figure how the merge broke it so it does
>> not happen again...
>>
>> steved.
>>
>
> Here was the original patch posting:
>
> http://www.spinics.net/lists/linux-nfs/msg07718.html
>
> I checked my mail archives and didn't see emails where we discussed
> this patch specifically around that time. Maybe we did on IRC before
> you merged it and I misunderstood what you intended to change? Hard to
> remember since it was over a year ago...
I generally just cut and paste the patches and if
I make any changes I post them... So I'm wondering
how that got changed... anyway... its fixed now...
steved.
next prev parent reply other threads:[~2010-10-28 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 1:29 [PATCH] nfs-utils: fix default value for --enable-tirpc Jeff Layton
2010-10-12 17:44 ` J. Bruce Fields
2010-10-28 13:24 ` Steve Dickson
2010-10-28 13:38 ` Jeff Layton
2010-10-28 14:03 ` Steve Dickson [this message]
2010-11-01 12:11 ` Steve Dickson
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=4CC9829E.90709@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.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.