From: "Weiwei Shu" <shuww1980@gmail.com>
To: git@vger.kernel.org
Subject: how to configure Git to treat certain type of ascii files as binary files
Date: Wed, 22 Oct 2008 16:58:28 -0500 [thread overview]
Message-ID: <65d12cb10810221458j14ef0009u679cdb0f73299d7f@mail.gmail.com> (raw)
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?
--
Weiwei
--Hope Springs Eternal.
next reply other threads:[~2008-10-22 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 21:58 Weiwei Shu [this message]
2008-10-22 22:13 ` how to configure Git to treat certain type of ascii files as binary files david
2008-10-22 22:35 ` Weiwei Shu
2008-10-22 22:13 ` David Symonds
2008-10-22 22:40 ` Jakub Narebski
2008-10-23 1:12 ` Weiwei Shu
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=65d12cb10810221458j14ef0009u679cdb0f73299d7f@mail.gmail.com \
--to=shuww1980@gmail.com \
--cc=git@vger.kernel.org \
/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).