From: Michael J Gruber <git@drmicha•warpmail.net>
To: Ping Yin <pkufranky@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: git adds some text file as binary file by mistake
Date: Fri, 24 Oct 2008 15:51:25 +0200 [thread overview]
Message-ID: <4901D2DD.8050704@drmicha.warpmail.net> (raw)
In-Reply-To: <46dff0320810240630s5cbfa62esd10a9da45ce37bf8@mail.gmail.com>
Ping Yin venit, vidit, dixit 24.10.2008 15:30:
> On Fri, Oct 24, 2008 at 8:54 PM, Michael J Gruber
> <git@drmicha•warpmail.net> wrote:
>> Ping Yin venit, vidit, dixit 24.10.2008 14:37:
>>> So what should i do if i want it added as text file?
>> You should give us more detail on the file ;)
>> What's the extension, what's the typical content? It may be a simple
>> matter of specifying attributes.
>> Do ordinary diff and grep recognize your files as text?
>>
>> Michael
>>
>
> It's just an xml file. I guess maybe there are some hidden characters
> at the beginning. I will figure it out later because i have no access
> to that file right now.
Maybe it's in an encoding which is not available on the machine you're
using git on?
> I'm just ask this problem in general sense. So is there a general way
> to specify whether a file is text or binary?
Bruce suggested a good read. To save you some time: You want to say
*.xml diff
or
*.xml diff crlf
in one of the attributes files, depending on whether you want git to
possibly translate line endings (which depends on other settings also).
Note that the "content type" of the file plays a role only for diffs and
stats, not for the actual storage (except for, possibly, crlf conversion).
Cheers,
Michael
next prev parent reply other threads:[~2008-10-24 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 12:37 git adds some text file as binary file by mistake Ping Yin
2008-10-24 12:54 ` Michael J Gruber
2008-10-24 13:30 ` Ping Yin
2008-10-24 13:34 ` Bruce Stephens
2008-10-24 13:51 ` Michael J Gruber [this message]
2008-10-30 6:32 ` Ping Yin
2008-10-31 0:29 ` Robin Rosenberg
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=4901D2DD.8050704@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=pkufranky@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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