Re: Always corrupt? what's the problem when CVS handles binary file?
From: Tommy Reynolds (TommyReynolds_at_yahoo.com)
Date: 08/17/04
- Previous message: Ivan Marsh: "Re: Add a scanner - how?"
- In reply to: lucy: "Always corrupt? what's the problem when CVS handles binary file?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 16 Aug 2004 17:36:05 -0500
On Mon, 16 Aug 2004 11:35:16 -0700, lucy wrote:
> Our group has set the option in the wrapperfiles to treat this kind of
> ".fig" file to be "binary"... We have stored this wrapperfile in the
> CVSROOT.
Please show us the content of your $CVSROOT/CVSROOT/cvswrappers file.
> cvs admin -kb [filename]
This alone should be sufficient.
> Both file is corrupted.
The "-kb" switch doesn't really change anything about a file during
the "cvs add" or "cvs import" step, it just controls how the file gets
mangled (or not) during a checkout; it's also used by the "cvs diff" command.
Try this:
1) Get some binary data:
$ dd if=/dev/random of=foo bs=1k count=1
$ cp foo foo.orig
2) cvs add foo
3) cvs commit -mNew foo
4) cvs admin -kb foo
5) rm foo
6) cvs update foo
7) cmp foo foo.orig
HTH.
- Previous message: Ivan Marsh: "Re: Add a scanner - how?"
- In reply to: lucy: "Always corrupt? what's the problem when CVS handles binary file?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
