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

Re: [PATCH 2/2] Documentation/SubmittingPatches: unify whitespace/tabs for the DCO

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 22, 2014, 17:55 UTC
Message-ID
<xmqqsig7a7rk.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1418864895-18583-3-git-send-email-sbeller@google.com>
Stefan Beller <sbeller@google.com> writes:
Show 9 quoted lines
> The Developers Certificate of Origin has a mixture of tabs and white
> spaces which is annoying to view if your editor explicitly views white
> space characters.
>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
>
> Notes:
>     I'll also try to send it upstream to linux.
Thanks.
Show 30 quoted lines
>
>  Documentation/SubmittingPatches | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 16b5d65..6124f34 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -258,15 +258,15 @@ pretty simple: if you can certify the below:
>              person who certified (a), (b) or (c) and I have not modified
>              it.
>  
> -	(d) I understand and agree that this project and the contribution
> -	    are public and that a record of the contribution (including all
> -	    personal information I submit with it, including my sign-off) is
> -	    maintained indefinitely and may be redistributed consistent with
> -	    this project or the open source license(s) involved.
> +        (d) I understand and agree that this project and the contribution
> +            are public and that a record of the contribution (including all
> +            personal information I submit with it, including my sign-off) is
> +            maintained indefinitely and may be redistributed consistent with
> +            this project or the open source license(s) involved.
>  
>  then you just add a line saying
>  
> -	Signed-off-by: Random J Developer <random@developer.example.org>
> +        Signed-off-by: Random J Developer <random@developer.example.org>
>  
>  This line can be automatically added by Git if you run the git-commit
>  command with the -s option.
Previous: Stefan BellerNext: Junio C Hamano
Message 4 of 10 in “Documentation/SubmittingPatches: Explain the rationale of git notes”
  1. 1/2 Documentation/SubmittingPatches: Explain the rationale of git notesStefan Beller, Dec 18, 2014
  2. Documentation/SubmittingPatches: unify whitespace/tabs for the DCOStefan Beller, Dec 18, 2014
  3. 2/2 Documentation/SubmittingPatches: unify whitespace/tabs for the DCOStefan Beller, Dec 18, 2014
  4. Junio C HamanoDec 22, 2014
  5. Junio C HamanoDec 22, 2014
  6. Stefan BellerDec 29, 2014
  7. [PATCHv2] Documentation/SubmittingPatches: Explain the rationale of git notesStefan Beller, Dec 29, 2014
  8. Eric SunshineDec 29, 2014
  9. Stefan BellerDec 29, 2014
  10. Junio C HamanoDec 30, 2014

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.