From: David Brown <git@davidb.org>
To: git@vger.kernel.org
Subject: Re: binary safe?
Date: Fri, 4 Nov 2005 08:54:19 -0800 [thread overview]
Message-ID: <20051104165419.GA12145@old.davidb.org> (raw)
In-Reply-To: <46a038f90511031500p3d6ed433s6efe3f5a5e60bcf8@mail.gmail.com>
On Fri, Nov 04, 2005 at 12:00:54PM +1300, Martin Langhoff wrote:
> Yes it works, and cvsimport -k will do the right thing for you.
Unless it has changed from 0.99.9b, 'cvsimport -k' will very much scramble
some binary files. '-k' passes the '-kk' option which causes CVS to strip
the keywords down. It needs to pass -ko through if you want it to be able
to handle binary files.
However, since CVS (RCS really) can remember the state of this flag, it
does work to 'cvs admin -ko filename' beforehand, and then do the
cvsimport without the '-k' option.
Dave
next prev parent reply other threads:[~2005-11-04 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 22:02 binary safe? Randal L. Schwartz
2005-11-03 22:49 ` Junio C Hamano
2005-11-03 23:00 ` Martin Langhoff
2005-11-04 16:54 ` David Brown [this message]
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=20051104165419.GA12145@old.davidb.org \
--to=git@davidb.org \
--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).