From: Petr Stodulka <pstodulk@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: COPYING tabs vs whitespaces
Date: Mon, 8 Feb 2016 10:24:30 +0100 [thread overview]
Message-ID: <56B85ECE.4020607@redhat.com> (raw)
In-Reply-To: <xmqqsi18i8xv.fsf@gitster.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
On 4.2.2016 20:15, Junio C Hamano wrote:
> Petr Stodulka <pstodulk@redhat.com> writes:
>
>> I found that license file COPYING is different as compared with
>> http://www.gnu.org/licenses/gpl-2.0.txt If I pass over with
>> Linus's preamble, change is only about whitespaces - tabs
>> vs. space. Probably it's minor non-essential change, but some
>> projects do this change, so rather I ask about that.
>
> Interesting. I cannot quite connect "some projects do this change"
> and "so rather I ask". Are you asking why this project changed it?
Nope. I apologize for my czenglish. It means: From my colleagues I hear,
that some projects had same differences (tabs vs. spaces) in their copy
of the license file and they make it later equivalent with the one in
gnu.org. So I ask rather here / point out this difference, if you know
about that or you want to have same one.
Yes, I know, it's just about whitespaces.
Petr.
>
> After running "diff" between the two, I think the changes are only
> on the indented section title lines, and "git blame" tells us that
> the section title lines in the copy we have has always been that way
> since Linus added to it at 075b845a (Add a COPYING notice, making it
> explicit that the license is GPLv2., 2005-04-11).
>
> So, perhaps the copy Linus got originally had leading runs of spaces
> that are multiples-of-8-long unexpanded to leading tabs back then,
> or perhaps he did that unexpanding himself.
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-08 9:24 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 [this message]
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
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=56B85ECE.4020607@redhat.com \
--to=pstodulk@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).