From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 56C7E3858C66 for ; Tue, 7 Mar 2023 12:28:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 56C7E3858C66 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678192092; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fN4hBXFADkwHgUqBHI8q9BZGZVhK89B+qhfk1w/3790=; b=DaJ1gDFZJPCfkBc1hJpHR0Eur8nYtc5UAt6LU38lU8DhlZSVDoPM4Au1jRIgkUrLyF946r 6tXu697sqOaGPBijCWYURUAOGs08nAOaqDPGH8a8Uspx/RJ3xR1m2/RQ8jprTW0vGNh1lW RS05RoGKTtwl2knw+XIabMMBFpKc7vo= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-509-Q-xHdxU7MnO18xlckMNWlg-1; Tue, 07 Mar 2023 07:28:09 -0500 X-MC-Unique: Q-xHdxU7MnO18xlckMNWlg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 633DC185A794; Tue, 7 Mar 2023 12:28:09 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.80]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1DABD2166B26; Tue, 7 Mar 2023 12:28:08 +0000 (UTC) From: Florian Weimer To: Arsen =?utf-8?Q?Arsenovi=C4=87?= 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 References: <20230307102935.2882450-1-arsen@gentoo.org> <87fsagpz3g.fsf@oldenburg.str.redhat.com> <86o7p4wzan.fsf@gentoo.org> <87356gpxut.fsf@oldenburg.str.redhat.com> <86bkl4wy0v.fsf@gentoo.org> Date: Tue, 07 Mar 2023 13:28:06 +0100 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") Message-ID: <87y1o8oieh.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Arsen Arsenovi=C4=87: > Florian Weimer writes: > >> * Arsen Arsenovi=C4=87: >> >>> 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. also links to this form, so I think it's the right one. Thanks, Florian