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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 28, 2020, 19:19 UTC
Message-ID
<xmqq35zpg2li.fsf@gitster.c.googlers.com>
In-Reply-To
<5fe9e731de0e5_209d20845@natae.notmuch>
Felipe Contreras <felipe.contreras@gmail.com> writes:
>> -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:
Yes, dropping "can" would be a good clarification, I would think, too.
>
>>  [[dco]]
>>  .Developer's Certificate of Origin 1.1
>>  ____
Previous: Felipe ContrerasNext: Derrick Stolee
Message 3 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.