From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH rdma-core] Improve global COPYING files
Date: Thu, 29 Sep 2016 10:16:59 -0600 [thread overview]
Message-ID: <20160929161659.GA774@obsidianresearch.com> (raw)
In-Reply-To: <20160929160053.GA11879-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On Thu, Sep 29, 2016 at 09:00:53AM -0700, Christoph Hellwig wrote:
> Hi Jason,
>
> any chance you could simply follow the modern debian copyright file
> format:
I was thinking about doing that.. But choose not to for this first
draft.
1) I'd have to go and unwind on a file by file basis exactly what
every licnese is. Right now I've just done a survey. There are many
copyrightable files with no license text, and many potentially
non-copyrightable files with no license text as well. All that
needs to be figured out first.
I would like to add at least short license headers to every file.
2) It seems to require listing the copyright owners for every file,
this is a royal pain, IMHO. Many copyrightable files do not have
copyright data, so it would have to be mined out of git. I have
a script that does that someplace..
My thinking was to start small, document the survey results (and agree
my interpetation is sensible), then work on achiveing full copyright
headers, then use that to build the debian format.
I'd appreciate help, eg patches moving toward #1 and eliminating the
free COPYING files and unlicnesed items. I think it will take a bit to
get there, I still have a bit wack of patches to get applied on other
topics..
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-29 16:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 4:13 [PATCH rdma-core] Improve global COPYING files Jason Gunthorpe
[not found] ` <20160923041340.GA11269-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-23 8:06 ` Leon Romanovsky
[not found] ` <20160923080655.GM4088-2ukJVAZIZ/Y@public.gmane.org>
2016-09-23 15:24 ` Jason Gunthorpe
[not found] ` <20160923152412.GB11269-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-23 17:10 ` Leon Romanovsky
[not found] ` <20160923171003.GR4088-2ukJVAZIZ/Y@public.gmane.org>
2016-09-23 17:23 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB08E66F-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-09-23 17:48 ` Jason Gunthorpe
[not found] ` <20160923174848.GC13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-29 15:53 ` Doug Ledford
2016-09-23 17:34 ` Jason Gunthorpe
[not found] ` <20160923173421.GB13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-05 12:49 ` Leon Romanovsky
[not found] ` <20161005124939.GF9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-06 4:30 ` Leon Romanovsky
2016-09-23 16:58 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB08E609-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-09-23 17:03 ` Jason Gunthorpe
[not found] ` <20160923170314.GA13920-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-23 17:12 ` Leon Romanovsky
2016-09-29 16:00 ` Christoph Hellwig
[not found] ` <20160929160053.GA11879-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-09-29 16:16 ` Jason Gunthorpe [this message]
[not found] ` <20160929161659.GA774-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-29 16:26 ` Doug Ledford
[not found] ` <57ED40C8.901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-29 22:55 ` Jason Gunthorpe
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=20160929161659.GA774@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.