From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix /proc pathname sizes on Solaris
Date: Wed, 19 Sep 2018 15:16:00 -0000 [thread overview]
Message-ID: <238c5f57-7f23-1e34-fe52-a5235a8a59d7@redhat.com> (raw)
In-Reply-To: <yddlg80nrhk.fsf@CeBiTec.Uni-Bielefeld.DE>
On 09/17/2018 03:11 PM, Rainer Orth wrote:
> * AFAIK Oracle has a corporate copyright assignment on file, so the
> patches should be covered.
It is my understanding that an assignment alone is not sufficient.
The patches should be willfully contributed somehow too. The most
common form is by the author or representative contributing or
disclaiming it on the list of course.
> Even if that were not the case, this one
> and the next are certainly below the 15-line limit for non-trivial
> patches.
That certainly helps.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-09-19 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 14:11 Rainer Orth
2018-09-17 18:35 ` Joel Brobecker
2018-09-17 19:27 ` Rainer Orth
2018-09-19 9:04 ` Rainer Orth
2018-09-19 13:21 ` Joel Brobecker
2018-09-19 12:58 ` Tom Tromey
2018-09-19 13:28 ` Rainer Orth
2018-09-19 15:16 ` Pedro Alves [this message]
2018-09-19 17:42 ` Rainer Orth
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=238c5f57-7f23-1e34-fe52-a5235a8a59d7@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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