Re: how to configure Git to treat certain type of ascii files as binary files

From: Weiwei Shu <shuww1980@gmail.com>
Date: Oct 23, 2008, 01:12 UTC
Message-ID: <65d12cb10810221812n692f83fl3b822568384f3f34@mail.gmail.com>
In-Reply-To: <m3hc74i73a.fsf@localhost.localdomain>

Thanks Jakub. I'll read its manual and try to play with it. Thank all for replies!

On Wed, Oct 22, 2008 at 5:40 PM, Jakub Narebski <jnareb@gmail.com> wrote:

Show 26 quoted lines

> "Weiwei Shu" <shuww1980@gmail.com> writes:
>
>> My first post in this mailing list. Could some one direct me to some
>> document/manual pages to setup Git to treat ascii files as binary
>> files? I'm using Git to do circuit schematics (SPICE files)
>> versioning. I will not do any merging or editing stuff with external
>> editors. The only way to change it is to use schematic capture GUIs
>> (Cadence, ADS, etc). So I'd like to treat them as binary files to
>> reduce the possibilities of messing them up.
>>
>> I know it seems a little bit stupid to use Git to do such an easy job.
>> But hey, it's the most eye-catching SCM software, isn't it?
>
> First, git does not modify files unless you have core.crlf set,
> and even then it warns about irreversible transformations
> (core.safecrlf)
>
> Second, using gitattributes you can set diff driver and merge driver;
> one of possibilities is to treat file as binary (binary diff and no
> using 3-way file merge).
>
> --
> Jakub Narebski
> Poland
> ShadeHawk on #git
>

-- 
Weiwei
--Hope Springs Eternal.