Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: David Miller <davem@davemloft.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	chuck.lever@oracle.com, bfields@fieldses.org, trond@netapp.com,
	linux-nfs@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net/sunrpc/xprtsock.c: some common code found
Date: Sat, 07 Feb 2009 12:22:01 -0500	[thread overview]
Message-ID: <1234027321.17241.25.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0902071831210.2805@wrl-59.cs.helsinki.fi>

On Sat, 2009-02-07 at 18:56 +0200, Ilpo J=C3=A4rvinen wrote:
> Can you please tell if you're still under impression that there wasn'=
t
> any changelog? What about those other guys who raised their concerns?
> (I can certainly understand why this impression might develop but it'=
s a=20
> problem in the canonial patch format, not in my actual changelog, I e=
ven=20
> need to circumvent ^--- by adding a space the to prevent tools for ma=
king=20
> a mistake). It will make a lot more sense after getting applied.
> ...Because there certainly was a changelog, and I didn't have any=20
> diffstat output there in the changelog?!? The output that *is* in the=
=20
> changelog is supposed to *help* the reviewer to see what will be stil=
l=20
> necessary to keep in the separate functions, but I guess people misse=
d=20
> that because the changelog looks too similar to what you will categor=
ize=20
> as patch (diff-funcs uses output which is familiar to all who who dea=
l=20
> with patches, and that's for purpose!).

If Chuck and Bruce are happy with it, then there is no problem, however
I have yet to see an acked-by from either one of them. My point is that
the process for accepting patches into the kernel involves ensuring tha=
t
there is consensus. It does not allow for one group to ride roughshod
over the objections of another.

   Trond
--=20
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

  reply	other threads:[~2009-02-07 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0902062247500.31842@wrl-59.cs.helsinki.fi>
     [not found] ` <Pine.LNX.4.64.0902062251501.31842@wrl-59.cs.helsinki.fi>
     [not found]   ` <20090206212043.GA1216@fieldses.org>
     [not found]     ` <20090206.140714.201930500.davem@davemloft.net>
     [not found]       ` <CAF18546-B024-40C9-8276-8FCD89C98E72@oracle.com>
2009-02-06 22:58         ` [PATCH] net/sunrpc/xprtsock.c: some common code found Ilpo Järvinen
     [not found]           ` <Pine.LNX.4.64.0902070040530.31875-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2009-02-07  3:22             ` David Miller
2009-02-07 16:23               ` Trond Myklebust
     [not found]                 ` <1234023804.17241.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-07 16:56                   ` Ilpo Järvinen
2009-02-07 17:22                     ` Trond Myklebust [this message]
     [not found]                       ` <1234027321.17241.25.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-08  3:00                         ` David Miller
     [not found]                     ` <Pine.LNX.4.64.0902071831210.2805-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2009-02-08  5:25                       ` J. Bruce Fields
2009-02-09 17:29                         ` Chuck Lever
2009-02-10 13:12                           ` Ilpo Järvinen
     [not found]                             ` <Pine.LNX.4.64.0902101417550.31742-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2009-02-10 17:12                               ` Chuck Lever
2009-02-10 13:20                         ` Ilpo Järvinen
2009-02-10 22:28                           ` 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=1234027321.17241.25.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trond@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