Re: Small question on "CVS Diff"

Robert,


> But that isn't how things actually are, and so I expect (apparently 
> incorrectly WRT at least CVS) my storage system to have some sense of 
> what my bits actually looked like when it first saw them, and 
> to be able 
> to reconstitute them exactly that way... sort of like MP3 vs 
> FLAC when 
> talking about sound recordings - FLAC can recreate the exact 
> wave data that was on the digital medium.

And just like your DVD player bought in year 2000 can only play MPEG2
content you need to upgrade it if you want MPEG4 or FLAC to something
designed more recently ;)

Based on the explanation of your workflow I personally think you should
stop trying to make CVS write the files in these odd formats and instead
use some other program to convert the format when you DO need to ship
them to other people.  Alternatively - DOS is so common now most non-DOS
platforms have efficient tools for converting DOS files to native
formats (dos2unix etc).

I think CVSNT or TortoiseCVS could do a better job of facilitating this
(eg: some 'send this sandbox' options, including a tar/gz option that
doesn't require cygwin to be installed).  

   cvs lexport --tounix c:\this.tgz .

This would create c:\this.tgz from the sandbox (using the CVS ignore
rules), in tar/gzip format and convert 'text' files to LF endings

However some people could argue this is rather out of scope...


Regards,


Arthur Barrett

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev