public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>
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:18:40 +0100	[thread overview]
Message-ID: <86bkl4wy0v.fsf@gentoo.org> (raw)
In-Reply-To: <87356gpxut.fsf@oldenburg.str.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]


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.

> Or we can take a DCO contribution from you today.  We don't need the
> assignment paperwork anymore.
>
>> PS: I noticed that I forgot to drop `,nptl' from the subject line.  The
>> NPTL bits of this patch are gone now.
>
> Ah, okay.
>
> Thanks,
> Florian


-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]

  reply	other threads:[~2023-03-07 12:23 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ć [this message]
2023-03-07 12:28         ` Florian Weimer
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=86bkl4wy0v.fsf@gentoo.org \
    --to=arsen@gentoo.org \
    --cc=carlos@redhat.com \
    --cc=fweimer@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).