git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: [PATCH] SubmittingPatches: tighten wording on "sign-off" procedure

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Dec 28, 2020, 14:09 UTC
Message-ID
<5fe9e731de0e5_209d20845@natae.notmuch>
In-Reply-To
<xmqqh7o6jjt1.fsf@gitster.c.googlers.com>
Junio C Hamano wrote:
> The text says "if you can certify DCO then you add a Singed-off-by
> trailer".  But it does not say anything about people who cannot
> certify.  A natural reading may be that if you cannot certify, you
> do not add the trailer, but it shouldn't hurt to be overly explicit.

It doesn't matter if a person *can* certify, what matters is if the person *does* certify.

In a weeding ceremony when asked "do you take this woman to be your wife?", the answer that is looked for is not "I can".

Do you or don't you? Is the question.
Show 10 quoted lines
> diff --git c/Documentation/SubmittingPatches w/Documentation/SubmittingPatches
> index d12094bac5..b091730771 100644
> --- c/Documentation/SubmittingPatches
> +++ w/Documentation/SubmittingPatches
> @@ -307,35 +307,35 @@ wrote the patch or have the right to pass it on under the same license
>  as ours, by "signing off" your patch.  Without sign-off, we cannot
>  accept your patches.
>  
> -If you can certify the below D-C-O:
> +If (and only if) you can certify the below D-C-O:
If you certify the bellow D-C-O:
>  [[dco]]
>  .Developer's Certificate of Origin 1.1
>  ____
-- 
Felipe Contreras
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 5 in “SubmittingPatches: tighten wording on "sign-off" procedure”
  1. SubmittingPatches: tighten wording on "sign-off" procedureJunio C Hamano, Dec 28, 2020
  2. Felipe ContrerasDec 28, 2020
  3. Junio C HamanoDec 28, 2020
  4. Derrick StoleeDec 28, 2020
  5. SubmittingPatches: tighten wording on "sign-off" procedureJunio C Hamano, Jan 7, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.