git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add gitattributes file making whitespace checking pickier
Date: Sun, 10 Feb 2008 19:34:01 -0800	[thread overview]
Message-ID: <7vk5lcb1zq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0802101724170.13593@iabervon.org> (Daniel Barkalow's message of "Sun, 10 Feb 2008 17:34:17 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> On Sun, 10 Feb 2008, Junio C Hamano wrote:
> ...
>> True, how about this instead?
>
> That makes things more clear, although I'd still like a t/.gitattributes 
> that meant that, regardless of the project's policies in general, t/ files 
> may care about whitespace, so we don't have to worry about that in future 
> changes to the top level .gitattributes.

Ok, that's sensible.

This is what I'll apply.  We can tighten and/or loosen per type
of the contents as we discover glitches.

--

 .gitattributes               |    2 ++
 Documentation/.gitattributes |    1 +
 t/.gitattributes             |    1 +
 3 files changed, 4 insertions(+), 0 deletions(-)
 create mode 100644 .gitattributes
 create mode 100644 Documentation/.gitattributes
 create mode 100644 t/.gitattributes

diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000..6b9c715
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1,2 @@
+* whitespace=!indent,trail,space
+*.[ch] whitespace
diff --git a/Documentation/.gitattributes b/Documentation/.gitattributes
new file mode 100644
index 0000000..ddb0301
--- /dev/null
+++ b/Documentation/.gitattributes
@@ -0,0 +1 @@
+*.txt whitespace
diff --git a/t/.gitattributes b/t/.gitattributes
new file mode 100644
index 0000000..562b12e
--- /dev/null
+++ b/t/.gitattributes
@@ -0,0 +1 @@
+* -whitespace

  reply	other threads:[~2008-02-11  3:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 16:22 [PATCH] Add gitattributes file making whitespace checking pickier J. Bruce Fields
2008-02-09 17:56 ` Daniel Barkalow
2008-02-09 18:50   ` J. Bruce Fields
2008-02-09 19:05     ` J. Bruce Fields
2008-02-09 19:36       ` Jakub Narebski
2008-02-09 20:04         ` J. Bruce Fields
2008-02-09 20:22           ` Jakub Narebski
2008-02-09 23:39             ` J. Bruce Fields
2008-02-09 20:57     ` Junio C Hamano
2008-02-09 23:36       ` J. Bruce Fields
2008-02-09 23:45       ` Jakub Narebski
2008-02-10  4:01         ` Junio C Hamano
2008-02-10 11:31           ` Jakub Narebski
2008-02-10 21:52             ` Junio C Hamano
2008-02-10 10:52       ` Junio C Hamano
2008-02-10 18:56         ` J. Bruce Fields
2008-02-10 20:22         ` Daniel Barkalow
2008-02-10 21:47           ` Junio C Hamano
2008-02-10 22:34             ` Daniel Barkalow
2008-02-11  3:34               ` Junio C Hamano [this message]
2008-02-12  7:43         ` Brian Downing
2008-02-12 21:42           ` 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=7vk5lcb1zq.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=bfields@fieldses.org \
    --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 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).