From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix /proc pathname sizes on Solaris
Date: Wed, 19 Sep 2018 17:42:00 -0000 [thread overview]
Message-ID: <yddsh25gz9q.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <238c5f57-7f23-1e34-fe52-a5235a8a59d7@redhat.com> (Pedro Alves's message of "Wed, 19 Sep 2018 16:16:54 +0100")
Hi Pedro,
> 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.
I wasn't aware of that. In case any of the remaining patches from the
solaris-userland repo prove fit for submission, I'll check how this can
be done, given that the authors are no longer with Oracle.
>> 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.
On top of that, both patches clearly document the intent already:
$ head 001-fix-proc-name-size.patch
#
# Fix the size of the pathname for /proc files.
# In Solaris, PID_MAX is 999999 (6 digit pid).
# In Solaris, lwpid_t is an unsigned int, so theoretically the lwp id
# could be 10 digits.
# Patch will be submitted upstream.
$ head 007-solib-svr4.patch
# Patch required for Solaris.
# Will contribute upstream if possible.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2018-09-19 17:42 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
2018-09-19 17:42 ` Rainer Orth [this message]
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=yddsh25gz9q.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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