git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation/SubmittingPatches: unify whitespace/tabs for the DCO
Date: Mon, 22 Dec 2014 09:55:59 -0800	[thread overview]
Message-ID: <xmqqsig7a7rk.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1418864895-18583-3-git-send-email-sbeller@google.com> (Stefan Beller's message of "Wed, 17 Dec 2014 17:08:15 -0800")

Stefan Beller <sbeller@google.com> writes:

> 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.

>
>  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.

  reply	other threads:[~2014-12-22 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <xmqq1tnx961q.fsf@gitster.dls.corp.google.com>
2014-12-18  1:08 ` [PATCH 1/2] Documentation/SubmittingPatches: Explain the rationale of git notes Stefan Beller
2014-12-18  1:08   ` [PATCH] Documentation/SubmittingPatches: unify whitespace/tabs for the DCO Stefan Beller
2014-12-18  1:08   ` [PATCH 2/2] " Stefan Beller
2014-12-22 17:55     ` Junio C Hamano [this message]
2014-12-22 17:55   ` [PATCH 1/2] Documentation/SubmittingPatches: Explain the rationale of git notes Junio C Hamano
2014-12-29 17:36     ` Stefan Beller
2014-12-29 17:42     ` [PATCHv2] " Stefan Beller
2014-12-29 23:18       ` Eric Sunshine
2014-12-29 23:21         ` Stefan Beller
2014-12-30 16:19           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqsig7a7rk.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).