From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-core] libibumad/sysfs.h: Add copyright
Date: Tue, 18 Oct 2016 12:07:45 -0700 [thread overview]
Message-ID: <20161018190745.GA26381@infradead.org> (raw)
In-Reply-To: <c1796e9a-32dc-62d2-481d-7decdc87700b-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On Tue, Oct 18, 2016 at 02:53:44PM -0400, Hal Rosenstock wrote:
> On 10/18/2016 2:43 PM, Christoph Hellwig wrote:
> > That seems like an odd copyright statement for a file that I created..
> >
> > While the delcarations came from another file the whitespaces and
> > oinclude headers take up just as little lines and have just as little
> > substance..
>
> What's the best thing to do ?
Just not bother with copyright notices for trivial files. E.g. we don't
bother with one for README.md or rdma-core.spec either.
--
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-10-18 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 17:20 [PATCH rdma-core] libibumad/sysfs.h: Add copyright Hal Rosenstock
[not found] ` <dfe69226-fb23-0bd5-c371-ad55c1356340-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-10-18 17:30 ` Leon Romanovsky
2016-10-18 18:43 ` Christoph Hellwig
[not found] ` <20161018184352.GA15413-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-10-18 18:53 ` Hal Rosenstock
[not found] ` <c1796e9a-32dc-62d2-481d-7decdc87700b-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-10-18 19:07 ` Christoph Hellwig [this message]
[not found] ` <20161018190745.GA26381-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-10-18 20:07 ` Hal Rosenstock
[not found] ` <f34c1ead-29ec-7968-e112-28af468c38de-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2016-10-18 20:37 ` Christoph Hellwig
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=20161018190745.GA26381@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox