git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH] Add gitattributes file making whitespace checking pickier
Date: Sat, 9 Feb 2008 11:22:35 -0500	[thread overview]
Message-ID: <20080209162234.GA25533@fieldses.org> (raw)

From: J. Bruce Fields <bfields@citi.umich.edu>

This will change the notion of "bad" whitespace for the git project to
include initial whitespace that uses spaces where tabs could have been
used.

This only changes which whitespace is considered "bad".  It doesn't
change the behavior when bad whitespace is found.  By default, commands
like git-apply, git-am, and git-rebase will print a warning but
otherwise do nothing.
---
 .gitattributes |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 .gitattributes

Is there any reason not to use this now that we have it?

diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000..dd65501
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1 @@
+* whitespace
-- 
1.5.4.rc2.60.gb2e62

             reply	other threads:[~2008-02-09 16:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 16:22 J. Bruce Fields [this message]
2008-02-09 17:56 ` [PATCH] Add gitattributes file making whitespace checking pickier 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
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=20080209162234.GA25533@fieldses.org \
    --to=bfields@fieldses.org \
    --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).