From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: binary safe?
Date: 03 Nov 2005 14:02:20 -0800 [thread overview]
Message-ID: <86br115r0z.fsf@blue.stonehenge.com> (raw)
I'm currently about to abandon CVS for my website management,
replacing it with git.
What problems, if any, will I have using git to manage the binary
files for my site, like the custom icons? CVS is doing that just fine
now.
I presume emailing diff-patches is out of the question, but if all I'm
doing is git-push and git-pull (using the shared central repository
model), and if I'm stupid enough to have a merge error it's OK to just
blow up on a binary file, will everything else work fine?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next reply other threads:[~2005-11-03 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 22:02 Randal L. Schwartz [this message]
2005-11-03 22:49 ` binary safe? Junio C Hamano
2005-11-03 23:00 ` Martin Langhoff
2005-11-04 16:54 ` David Brown
2005-11-04 21:22 ` Martin Langhoff
2005-11-04 21:27 ` David Brown
2005-11-03 22:50 ` Linus Torvalds
2005-11-04 3:49 ` Chris Wedgwood
2005-11-03 23:05 ` Nick Hengeveld
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=86br115r0z.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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).