From: Bruce Stephens <bruce.stephens@isode.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, 24 Oct 2008 14:34:34 +0100 [thread overview]
Message-ID: <80tzb2xgk5.fsf@tiny.isode.net> (raw)
In-Reply-To: <46dff0320810240630s5cbfa62esd10a9da45ce37bf8@mail.gmail.com> (Ping Yin's message of "Fri\, 24 Oct 2008 21\:30\:19 +0800")
"Ping Yin" <pkufranky@gmail.com> writes:
[...]
> I'm just ask this problem in general sense. So is there a general way
> to specify whether a file is text or binary?
Yes: gitattributes(5).
next prev parent reply other threads:[~2008-10-24 13:35 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 [this message]
2008-10-24 13:51 ` Michael J Gruber
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=80tzb2xgk5.fsf@tiny.isode.net \
--to=bruce.stephens@isode.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).