From: Florian Weimer <fw@deneb.enyo.de>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
libc-stable@sourceware.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [2.29 COMMITTED] regex: fix read overrun [BZ #24114]
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <87bm26fpso.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <569734858.135913.1553034460491@poczta.nazwa.pl> (Rafal Luzynski's message of "Tue, 19 Mar 2019 23:27:40 +0100 (CET)")
* Rafal Luzynski:
>> [...]
>> At commit/push time (not at contribution time), the copyright
>> assignment may no longer be in effect for new contributions from the
>> same person, after all.
>
> I am not a lawyer so I should not speak about it... But should the
> commit/push ever happen if the copyright assignment is no longer in
> effect?
I wrote “new contributions”. We deal with past contributions all the
time whose author would no longer be covered by a copyright assignment
for a hypothetical new contribution. Most of the time, these
contributions are already in the source tree, and we adapt them, but
not always. The usual cause of such discrepancies is when authors do
not enter copyright assignments with the FSF, but rely on their
employers' pre-existing assignments and the fact that the employer
owns the copyright in a work-for-hire scenario.
next prev parent reply other threads:[~2019-03-19 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Aurelien Jarno
2019-01-01 0:00 ` [2.29 COMMITTED] Record CVE-2019-9169 in NEWS and ChangeLog " Aurelien Jarno
2019-01-01 0:00 ` [2.29 COMMITTED] regex: fix read overrun " Rafal Luzynski
2019-01-01 0:00 ` Aurelien Jarno
2019-01-01 0:00 ` Rafal Luzynski
2019-01-01 0:00 ` Florian Weimer
2019-01-01 0:00 ` Rafal Luzynski
2019-01-01 0:00 ` Florian Weimer [this message]
2019-01-01 0:00 ` Paul Eggert
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=87bm26fpso.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=aurelien@aurel32.net \
--cc=digitalfreak@lingonborough.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-stable@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).