From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AC018E7D24C for ; Tue, 26 Sep 2023 08:00:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 1C56B82123; Tue, 26 Sep 2023 08:00:15 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 1C56B82123 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLUNZTlNV4Fo; Tue, 26 Sep 2023 08:00:14 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp1.osuosl.org (Postfix) with ESMTP id A63EF81258; Tue, 26 Sep 2023 08:00:12 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org A63EF81258 Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by ash.osuosl.org (Postfix) with ESMTP id 8EEA51BF33A for ; Tue, 26 Sep 2023 08:00:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 6630F82123 for ; Tue, 26 Sep 2023 08:00:10 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 6630F82123 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-5bOqHMHEyP for ; Tue, 26 Sep 2023 08:00:09 +0000 (UTC) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by smtp1.osuosl.org (Postfix) with ESMTPS id 328B88211F for ; Tue, 26 Sep 2023 08:00:08 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 328B88211F Received: by mail.gandi.net (Postfix) with ESMTPSA id 522FE4000F; Tue, 26 Sep 2023 08:00:04 +0000 (UTC) Received: from peko by dell.be.48ers.dk with local (Exim 4.94.2) (envelope-from ) id 1ql2zD-0032Hr-8S; Tue, 26 Sep 2023 10:00:03 +0200 From: Peter Korsgaard To: Giulio Benetti References: <20230917205107.366824-1-giulio.benetti@benettiengineering.com> <20230917205107.366824-2-giulio.benetti@benettiengineering.com> Date: Tue, 26 Sep 2023 10:00:03 +0200 In-Reply-To: <20230917205107.366824-2-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Sun, 17 Sep 2023 22:51:07 +0200") Message-ID: <8734z1weik.fsf@48ers.dk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-GND-Sasl: peter@korsgaard.com Subject: Re: [Buildroot] [PATCH 1/1] docs/manual: add section to explain how to give credits to a sponsor X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Thomas De Schampheleire , buildroot@buildroot.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" >>>>> "Giulio" == Giulio Benetti writes: > Sometimes it happens that a Company or a Physical Person sponsors the > creation and/or the upstreaming process of a patch, but at the moment > there is no way to give credits to it. In Linux they prepend '+sponsor' > to the e-mail of the contributor in both authorship and commit log tag as > discussed here[0]. So let's describe in the manual how to do that as a > standard. > [0]: > https://lore.kernel.org/linux-doc/20230817220957.41582-1-giulio.benetti@benettiengineering.com/ > Signed-off-by: Giulio Benetti Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks. -- Bye, Peter Korsgaard _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot