From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Michael J Gruber" <git@drmicha.warpmail.net>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git adds some text file as binary file by mistake
Date: Fri, 31 Oct 2008 01:29:16 +0100 [thread overview]
Message-ID: <200810310129.16847.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <46dff0320810292332y34ea0daemde05b58572946497@mail.gmail.com>
torsdagen den 30 oktober 2008 07.32.47 skrev Ping Yin:
> On Fri, Oct 24, 2008 at 9:30 PM, Ping Yin <pkufranky@gmail.com> wrote:
> > 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.
> >
> > Ping Yin
> >
>
> I have figured it out. It's just because the BOM characters feff00 in
> the beginning of the utf-8 xml file.
The UTF-8 BOM is EF BB BF, (no NUL.). FEFF is UTF-16 BE (and the third
byte would be 00 for an XML file). I think git currently regards just about
any UTF-16 file as binary becuase of the NUL bytes.
-- robin
prev parent reply other threads:[~2008-10-31 0:30 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
2008-10-30 6:32 ` Ping Yin
2008-10-31 0:29 ` Robin Rosenberg [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=200810310129.16847.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=pkufranky@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 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).