git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Stodulka <pstodulk@redhat.com>
To: Stefan Beller <sbeller@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: COPYING tabs vs whitespaces
Date: Tue, 9 Feb 2016 20:25:23 +0100	[thread overview]
Message-ID: <56BA3D23.8050506@redhat.com> (raw)
In-Reply-To: <CAGZ79kYaGDBunX8fFiEq0dD0Rq6vjZ3ttMnLZUmy3c7DhgfkOw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4451 bytes --]



On 9.2.2016 19:40, Stefan Beller wrote:
> As a reference for this discussion,
> see c376d96 in git.git or e00bfcbf04 in linux.git
> which deals with whitespaces in the developers certificate of origin.
> 
> Just send a patch, I'd say.
> 
> Thanks,
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Just patch makes from whole thread more and more absurd discussion, no offense.
Don't matter if it is used or not. For me it's significant previous response from Junio.

I am not familiar with git send-email, so:
=======================[PATCH 1/2]====================================
From b2509773edf7e886513f450cb8e215a87278cdfc Mon Sep 17 00:00:00 2001
From: Petr Stodulka <pstodulk@redhat.com>
Date: Tue, 9 Feb 2016 19:52:28 +0100
Subject: [PATCH 1/2] COPYING: replace tabs by spaces in license file

GPLv2 license file presented in gnu.org has replaced all tabs by spaces.
Unify whitespaces to make equivalent files (except preamble).
---
 COPYING | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/COPYING b/COPYING
index 536e555..158a9b1 100644
--- a/COPYING
+++ b/COPYING
@@ -19,15 +19,16 @@
 
 ----------------------------------------
 
-		    GNU GENERAL PUBLIC LICENSE
-		       Version 2, June 1991
+
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
 
  Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
  51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 
-			    Preamble
+                            Preamble
 
   The licenses for most software are designed to take away your
 freedom to share and change it.  By contrast, the GNU General Public
@@ -77,7 +78,7 @@ patent must be licensed for everyone's free use or not licensed at all.
   The precise terms and conditions for copying, distribution and
 modification follow.
 
-		    GNU GENERAL PUBLIC LICENSE
+                    GNU GENERAL PUBLIC LICENSE
    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
 
   0. This License applies to any program or other work which contains
@@ -276,7 +277,7 @@ make exceptions for this.  Our decision will be guided by the two goals
 of preserving the free status of all derivatives of our free software and
 of promoting the sharing and reuse of software generally.
 
-			    NO WARRANTY
+                            NO WARRANTY
 
   11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
 FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
@@ -298,9 +299,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
 PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
 POSSIBILITY OF SUCH DAMAGES.
 
-		     END OF TERMS AND CONDITIONS
+                     END OF TERMS AND CONDITIONS
 
-	    How to Apply These Terms to Your New Programs
+            How to Apply These Terms to Your New Programs
 
   If you develop a new program, and you want it to be of the greatest
 possible use to the public, the best way to achieve this is to make it
-- 
2.4.3


=======================[PATCH 2/2]====================================
From 5a7bfe0b05f35238c7bc8d2680b168ef729d0e91 Mon Sep 17 00:00:00 2001
From: Petr Stodulka <pstodulk@redhat.com>
Date: Tue, 9 Feb 2016 20:08:44 +0100
Subject: [PATCH 2/2] Unify tabs and spaces in preamble of COPYING file

---
 COPYING | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/COPYING b/COPYING
index 158a9b1..bc404d9 100644
--- a/COPYING
+++ b/COPYING
@@ -9,13 +9,13 @@
  decision, you might note so in your copyright message, ie something
  like
 
-	This file is licensed under the GPL v2, or a later version
-	at the discretion of Linus.
+    This file is licensed under the GPL v2, or a later version
+    at the discretion of Linus.
 
   might avoid issues. But we can also just decide to synchronize and
   contact all copyright holders on record if/when the occasion arises.
 
-			Linus Torvalds
+            Linus Torvalds
 
 ----------------------------------------
 
-- 
2.4.3



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-02-09 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 10:45 COPYING tabs vs whitespaces Petr Stodulka
2016-02-04 19:15 ` Junio C Hamano
2016-02-08  9:24   ` Petr Stodulka
2016-02-08 17:28     ` Junio C Hamano
2016-02-08 22:11       ` Petr Stodulka
2016-02-09 18:40         ` Stefan Beller
2016-02-09 19:25           ` Petr Stodulka [this message]

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=56BA3D23.8050506@redhat.com \
    --to=pstodulk@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).