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

From: Weiwei Shu <shuww1980@gmail.com>
Date: Oct 22, 2008, 22:35 UTC
Message-ID: <65d12cb10810221535l235490b9ifc39738c0cde5f4d@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.10.0810221511590.24463@asgard.lang.hm>

Thanks David.

Well, for binary files, SCM tools (like subversion) usually work as "lock-modify-unlock" mode in which merging is not supported since the files are not human-readable. The schematics are ascii files, but I do not want them to be merged if I run "merge" command. Instead I'd like Git ask me to "look-and-replace". I know Git is not meant to do this kind of jobs. Just curious if it is able to be configured to work in that way.

On Wed, Oct 22, 2008 at 5:13 PM,  <david@lang.hm> wrote:

Show 22 quoted lines

> On Wed, 22 Oct 2008, Weiwei Shu wrote:
>
>> Hello everyone,
>>
>> 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?
>
> unless you enable cr/lf handling git won't change ascii files.
>
> what is it that you think needs to be done differently for these files than
> for any other files?
>
> David Lang
>

-- 
Weiwei
--Hope Springs Eternal.