From: Petr Stodulka <pstodulk@redhat.com>
To: git@vger.kernel.org
Subject: COPYING tabs vs whitespaces
Date: Thu, 4 Feb 2016 11:45:46 +0100 [thread overview]
Message-ID: <56B32BDA.4010909@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
Hi,
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.
Regards,
Petr
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-02-04 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 10:45 Petr Stodulka [this message]
2016-02-04 19:15 ` COPYING tabs vs whitespaces 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
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=56B32BDA.4010909@redhat.com \
--to=pstodulk@redhat.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.