All of lore.kernel.org
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: Stefan Karpinski <stefan.karpinski@gmail.com>
Cc: Jonathan del Strother <maillist@steelskies.com>,
	Alex Riesen <raa.lkml@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: builtin conversion between tabs and spaces
Date: Wed, 15 Oct 2008 19:34:33 -0400	[thread overview]
Message-ID: <48F67E09.90202@gmail.com> (raw)
In-Reply-To: <d4bc1a2a0810151602j56550c3di2f59f92039fa8243@mail.gmail.com>

Stefan Karpinski wrote:
> Any further comments? I'm more than willing to implement this, but I
> won't bother if there's no chance of getting it accepted as a patch.
> Does no one else feel like at least having the option to enforce
> whitespace consistency in git is a good thing? If not, I guess I'll
> just muddle along without this feature instead of implementing it.

I'm against including this in except as a sample smudge/clean script. 
Git is a content tracker; not the enforcement mechanism for individual 
project policies.

  reply	other threads:[~2008-10-15 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d4bc1a2a0810141839r547a770j3a8e56312afa6a53@mail.gmail.com>
     [not found] ` <d4bc1a2a0810141842q1e50c85au7d813f2e5e37a84c@mail.gmail.com>
2008-10-15  1:44   ` builtin conversion between tabs and spaces Stefan Karpinski
2008-10-15  1:47     ` Stefan Karpinski
2008-10-15  6:25     ` Alex Riesen
2008-10-15 20:52       ` Stefan Karpinski
2008-10-15 21:02         ` Jonathan del Strother
2008-10-15 21:18           ` Stefan Karpinski
2008-10-15 23:02             ` Stefan Karpinski
2008-10-15 23:34               ` A Large Angry SCM [this message]
2008-10-16  2:00                 ` Stefan Karpinski
2008-10-15  6:26     ` Johannes Sixt
2008-10-15 20:55       ` Stefan Karpinski

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=48F67E09.90202@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=maillist@steelskies.com \
    --cc=raa.lkml@gmail.com \
    --cc=stefan.karpinski@gmail.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 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.