git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Frans Englich <fenglich@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: Bug report: .gitattributes: -diff Unset causes files to be reported as binaries
Date: Thu, 02 Jul 2009 16:29:07 +0200	[thread overview]
Message-ID: <4A4CC433.5040401@lsrfire.ath.cx> (raw)
In-Reply-To: <200907011208.35397.fenglich@fastmail.fm>

Frans Englich schrieb:
> Hi,
> 
> Applying -diff Unset to a file using .gittattributes causes "git diff" to 
> state that the file is a binary even though it isn't, or have been instructed 
> to be treated as one. See attached script for reproducing.
> 
> This causes confusion since the file isn't a binary, it's only the diff output 
> that has been suppressed. For instance, an auto generated cpp file has -diff 
> Unset applied to it to suppress the meaningless output, but people contact 
> you to point out the file is binary.

Generated files normally don't need to be tracked, as long as all their
sources are tracked and the tools to generate them are readily available
to your target audience.  So perhaps ceasing to track the files and
adding them to the file .gitignore instead is an option?

René

      parent reply	other threads:[~2009-07-02 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 10:08 Bug report: .gitattributes: -diff Unset causes files to be reported as binaries Frans Englich
2009-07-02  5:35 ` Jeff King
2009-07-02  8:14   ` Frans Englich
2009-07-02 11:12     ` Paolo Bonzini
2009-07-02 11:29       ` Frans Englich
2009-07-02 11:29         ` Paolo Bonzini
2009-07-02 17:05       ` Jeff King
2009-07-02 11:59     ` Jakub Narebski
2009-07-02 17:04     ` Jeff King
2009-07-02 14:29 ` René Scharfe [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=4A4CC433.5040401@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=fenglich@fastmail.fm \
    --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).