From: Ben Evans <bevans@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] LU-6402 MODULE_AUTHOR changes
Date: Thu, 3 Sep 2015 13:58:15 +0000 [thread overview]
Message-ID: <D20DBB55.B1C%jevans@cray.com> (raw)
My personal preference would be for OpenSFS to be listed, since Lustre development is a community effort, rather than a product of any specific company.
For example, I?d have no problem with Intel?s name on their next-gen interconnect lnd code, or with Cray?s name on the GNI code, etc. but the core parts of Lustre should belong to OpenSFS or EOFS.
-Ben Evans
From: lustre-devel <lustre-devel-bounces at lists.lustre.org<mailto:lustre-devel-bounces@lists.lustre.org>> on behalf of "Simmons, James A." <simmonsja at ornl.gov<mailto:simmonsja@ornl.gov>>
Date: Wednesday, September 2, 2015 at 5:29 PM
To: "lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>" <lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>>
Subject: [lustre-devel] LU-6402 MODULE_AUTHOR changes
For the LU-6402 the modinfo is pretty stale so I send up a patch at http://review.whamcloud.com/#/c/16132. Andreas brought the topic of who
should the MODULE_AUTHOR be. Currently it is Sun Inc which is not the case. I changed it to Intel but not might not be the right choice anymore.
So what should the MODULE_AUTHOR be?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150903/fa4e0bad/attachment.htm>
next reply other threads:[~2015-09-03 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 13:58 Ben Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-02 22:29 [lustre-devel] LU-6402 MODULE_AUTHOR changes Simmons, James A.
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=D20DBB55.B1C%jevans@cray.com \
--to=bevans@cray.com \
--cc=lustre-devel@lists.lustre.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.