public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: git whitespace test
Date: Mon, 15 Jun 2009 16:19:00 -0000	[thread overview]
Message-ID: <877hzdjwqg.fsf@meyering.net> (raw)
In-Reply-To: <4A3673E3.9020908@redhat.com> (Ulrich Drepper's message of "Mon, 15 Jun 2009 09:16:35 -0700")

Ulrich Drepper wrote:
> Jim Meyering wrote:
>> How about an alternative: use a .gitattributes file to exempt just
>> those files.  Then we can turn the global hook back on, and relax
>> policy as needed by modifying .gitattributes.
>
> If this works, sure.

Ok.  I've pushed the .gitattributes-adding patch (without
the ChangeLog entry, as you requested) and reverted
the server-side setting to hooks.allowbadwhitespace=false.

      reply	other threads:[~2009-06-15 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 15:59 Ulrich Drepper
2009-06-15 16:06 ` Jim Meyering
2009-06-15 16:16   ` Ulrich Drepper
2009-06-15 16:19     ` Jim Meyering [this message]

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=877hzdjwqg.fsf@meyering.net \
    --to=jim@meyering.net \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).