From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 4F706138334 for ; Wed, 3 Oct 2018 19:28:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 12457E0A93; Wed, 3 Oct 2018 19:28:28 +0000 (UTC) Received: from mail-pg1-f193.google.com (mail-pg1-f193.google.com [209.85.215.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C5CACE0A92 for ; Wed, 3 Oct 2018 19:28:27 +0000 (UTC) Received: by mail-pg1-f193.google.com with SMTP id 80-v6so1994716pgh.10 for ; Wed, 03 Oct 2018 12:28:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=BI3hJhygubeFW8p16l6dlP6QLWpdJi5nVk0y2yX6G+o=; b=rNnaSro3yF6+iwT9CeG7StnTxalUUp+dsePPVzBKsIS0Q6pRZa1EcGMscL62Z9868k SRB6y1PQicw2Pb4bfHs+D3o3g8hDZeJGjhbWFx/xDPCLZIvGYPaap+YnEAtL1TbgEGne 7+VcrWbgjBLe1hlyHm+WtuovBnudxIwzAC/wxrvJ7vPTTKWyrBdcMcNqr0W7FEUUvz0Z bcohG/0GPlw4PM/eY0gK+WTcby6yET5LFvAUgLMkW1Ncvv9I0Au7vMwafPJPeyuzpdND B/BlllDh805KtmwbEV5kvppAIAYtR4ie44R0u8ZxOCqCW9WmZPFuRdvYY6tMX5ef5jjw 9/Yg== X-Gm-Message-State: ABuFfoiLzaZJiYtZK8KWy0q2d4jI0UtWHkoApJXpwq9o9OU+W4/Lm36h CHLmN+MS505b/tFKWLiy9xmKLXM+eEXihy6YstOgXpbA X-Google-Smtp-Source: ACcGV61brkx3Pg/i6shmBdvzrHzaV6+tGKqiMGPnGst9peJQuyA3cWRqWQGS7J+CtHJVr7xXqNi9VpuuT5NB2xdRCOc= X-Received: by 2002:a63:c5a:: with SMTP id 26-v6mr2683192pgm.372.1538594906246; Wed, 03 Oct 2018 12:28:26 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 References: <23325.35685.793702.267278@a1i15.kph.uni-mainz.de> <23337.15822.698153.812236@a1i15.kph.uni-mainz.de> <14e33478-835e-33ec-5d68-5ccb05fb2a9d@gmail.com> <72d18d67-1c32-33dd-8b62-fd7b3bdeba3c@gentoo.org> <20181003221615.88d543bde07109aae55e38c8@gentoo.org> In-Reply-To: <20181003221615.88d543bde07109aae55e38c8@gentoo.org> From: Rich Freeman Date: Wed, 3 Oct 2018 15:28:13 -0400 Message-ID: Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4] To: gentoo-project Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: d8458445-fd59-4748-9779-9e94215cf48c X-Archives-Hash: 2b88c3c6ad71cab606dc5a08851dfbd5 On Wed, Oct 3, 2018 at 3:16 PM Andrew Savchenko wrote: > > Sign-off usually means "I have reviewed this commit and approve it". > This is how it works in the Linux kernel where one have to collect > sufficient number of sign-offs to pass commit in the main tree. An > attempt to give it another meaning like "I'm the author of this > commit" looks questionable. Of course DCO certification is fine as > well. > In Linux kernel development signed-off-by has nothing to do with code reviews/approvals per se, and everything to do with the DCO. Documentation/process/submitting-patches.rst Simply giving approval without certifying the DCO is done with the Acked-by tag. Anybody in the process of forwarding the patch up to Linux has to append a Signed-off-by, because they're signing the DCO for that patch. A maintainer who isn't forwarding the patch would use Acked-by, since they didn't touch the patch and thus could not have introduced copyrightable changes. -- Rich