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

Re: [PATCH] am: add am.signoff add config variable

From
Jacob Keller <jacob.keller@gmail.com>
Date
Dec 29, 2016, 17:49 UTC
Message-ID
<A52AD4B5-8AB3-49E8-9EED-5ABBA91369D4@gmail.com>
In-Reply-To
<20161229084701.GA3643@starla>
On December 29, 2016 12:47:01 AM PST, Eric Wong <e@80x24.org> wrote:
Show 17 quoted lines
>Eduardo Habkost <ehabkost@redhat.com> wrote:
>> git-am has options to enable --message-id and --3way by default,
>> but no option to enable --signoff by default. Add a "am.signoff"
>> config option.
>
>I'm not sure this is a good idea.  IANAL, but a sign-off
>has some sort of legal meaning for this project (DCO)
>and that would be better decided on a patch-by-patch basis
>rather than a blanket statement.
>
>I don't add my SoB to patches (either my own or received) until
>I'm comfortable with it; and I'd rather err on the side of
>forgetting and being prodded to resubmit rather than putting
>an SoB on the wrong patch.
>
>
>(I'm barely online today, no rush needed in responding)
I don't know what is true for all projects, but I can't believe making it configurable would cause problems.... If you don't want it you don't have to enable it.
I suppose your argument is that we shouldn't ever make it automatically but... I know that many people who receive email patches, apply them, then forward those to another group add their sign off as a mark of "yes I certify that this is legally OK" so I think this would be useful.

Thanks Jake

Previous: Eduardo HabkostNext: Junio C Hamano
Message 6 of 11 in “am: add am.signoff add config variable”
  1. am: add am.signoff add config variableEduardo Habkost, Dec 28, 2016
  2. Stefan BellerDec 28, 2016
  3. Eduardo HabkostDec 28, 2016
  4. Eric WongDec 29, 2016
  5. Eduardo HabkostDec 29, 2016
  6. Jacob KellerDec 29, 2016
  7. Junio C HamanoDec 29, 2016
  8. Eduardo HabkostDec 29, 2016
  9. Stefan BellerDec 29, 2016
  10. Junio C HamanoDec 29, 2016
  11. Stefan BellerDec 29, 2016

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.