From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] idmapd: logging of Local-Realms only lists the last realm
Date: Mon, 19 Mar 2012 15:33:54 -0400 [thread overview]
Message-ID: <20120319193354.GG23670@fieldses.org> (raw)
In-Reply-To: <5295E5C7-2AD7-4D52-B3C1-8C24D964DCEF@oracle.com>
On Mon, Mar 19, 2012 at 01:43:52PM -0400, Chuck Lever wrote:
> My understanding is that SOB is not about responsibility, but about
> the provenance of the work. It doesn't matter how large or small the
> patch is.
Well, it can matter in some ways. For purposes of copyright, e.g., this
patch isn't likely to raise any issues.
> I've never seen another project maintainer drop an SOB like this, so
> I'm just asking (and copying the list for other opinions). No
> objection, just want to make sure we are dotting our open-source "i"s
> and so on.
I have, for small stuff. Or e.g. when a patch was written by a student
working with me and I saw previous revisions of it, so I'm willing to
vounch for it being their work.
And agreed with Steved on process--make it easy for the new and drive-by
contributors when it doesn't make extra work for the rest of us, and
they'll figure out the rest of the process later if they need to.
--b.
next prev parent reply other threads:[~2012-03-19 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 12:36 [PATCH 1/1] idmapd: logging of Local-Realms only lists the last realm Steve Dickson
2012-03-19 13:12 ` J. Bruce Fields
2012-03-19 14:05 ` Chuck Lever
2012-03-19 17:36 ` Steve Dickson
2012-03-19 17:43 ` Chuck Lever
2012-03-19 19:20 ` Steve Dickson
2012-03-19 19:33 ` J. Bruce Fields [this message]
2012-03-19 19:45 ` 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=20120319193354.GG23670@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.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.