public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Arsen Arsenović" <arsen@gentoo.org>
Cc: libc-alpha@sourceware.org,  carlos@redhat.com,  toolchain@gentoo.org
Subject: Re: [PATCH v3 1/2] elf,nptl: Add -z lazy to some more tests
Date: Tue, 07 Mar 2023 13:28:06 +0100	[thread overview]
Message-ID: <87y1o8oieh.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <86bkl4wy0v.fsf@gentoo.org> ("Arsen =?utf-8?Q?Arsenovi=C4=87?= =?utf-8?Q?=22's?= message of "Tue, 07 Mar 2023 13:18:40 +0100")

* Arsen Arsenović:

> Florian Weimer <fweimer@redhat.com> writes:
>
>> * Arsen Arsenović:
>>
>>> Yes, I never signed the copyright papers for the libc.
>>>
>>> I intended to undergo that process, which is why I didn't add signoffs
>>> initially (since they'd indicate that I don't intend to sign over
>>> copyright when I do), so I figured I should wait for advice.
>>>
>>> How should I proceed?
>>
>> It's up to you.  You can try the FSF paperwork process, it should be
>> fully digital nowadays.  And we can apply the patch as a regular FSF
>> contribution once the paperwork is complete.
>
> My previous experiences were rather prompt (usually done by the time I'm
> done with a patchset - not the case here due to the triviality, of
> course).  Is
> https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
> the right form?  This is the one I've used for gcc et al, to cover
> current and future changes of any nature.

<https://sourceware.org/glibc/wiki/CopyrightFSF> also links to this
form, so I think it's the right one.

Thanks,
Florian


  reply	other threads:[~2023-03-07 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 10:29 Arsen Arsenović
2023-03-07 10:29 ` [PATCH v3 2/2] elf: Add missing dependency between resolvfail and testobj1.so Arsen Arsenović
2023-03-07 11:42 ` [PATCH v3 1/2] elf,nptl: Add -z lazy to some more tests Florian Weimer
2023-03-07 11:53   ` Arsen Arsenović
2023-03-07 12:08     ` Florian Weimer
2023-03-07 12:18       ` Arsen Arsenović
2023-03-07 12:28         ` Florian Weimer [this message]
2023-03-07 18:47           ` Arsen Arsenović
2023-03-10 16:54     ` Florian Weimer
2023-03-10 17:17       ` Arsen Arsenović

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=87y1o8oieh.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=arsen@gentoo.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=toolchain@gentoo.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).