Greets,
I know that CVS is not the best place to store
binaries. However, I am trying to find a good solution for doing so.
I am hoping someone can help me in this decision.
I want to do revision control on files such as
Visio diagrams and Access applications. These files are "binary"
[ On Friday, October 26, 2001 at 10:48:20 (-0500), Jason Mowat wrote: ]
> Subject: CVS and Binaries
>
> I want to do revision control on files such as Visio diagrams and
> Access applications. These files are "binary" format. I am currently
> a user of CVS for my te
Ok its clear, that CVS is not for merging binaries.. But can I, theoretically,
make my own wrapper which converts the binary into some sort of
mergeable text (uuencode for example) which encodes binary before
it gets into repository, and reverts ir back when file is checked out?
I know it will t
The uuencode format is an example of an ASCII-but-unmergeable format.
In other words, after you've performed a merge between two or three
uuencoded files, the output will likely be unrecognizable by the
uudecode program.
You're better off using something that's better suited to storing
binaries.
> "Nils9" == Nils9 <[EMAIL PROTECTED]> writes:
Nils9> Ok its clear, that CVS is not for merging binaries.. But
Nils9> can I, theoretically, make my own wrapper which converts
Nils9> the binary into some sort of mergeable text (uuencode for
Nils9> example) which encodes binary
Sau Dan Lee <[EMAIL PROTECTED]> wrote:
>
> For your case, I think you'll be better of saving the binary
> files with names containing version numbers (manually assigned).
> There is no space lost with this method (since there is no generic
> way to diff two binary files to produce a mini
>--- Forwarded mail from [EMAIL PROTECTED]
>Sau Dan Lee <[EMAIL PROTECTED]> wrote:
>>
>> For your case, I think you'll be better of saving the binary
>> files with names containing version numbers (manually assigned).
>> There is no space lost with this method (since there is no generic
> "Guy" == Guy Scharf <[EMAIL PROTECTED]> writes:
Guy> Sau Dan Lee <[EMAIL PROTECTED]> wrote:
>> For your case, I think you'll be better of saving the binary
>> files with names containing version numbers (manually
>> assigned). There is no space lost with this method (since
