Proposal to fix CVS binary file implementation

2000-12-20 Thread David L. Martin
CVS'ers,   A binary file is a binary file.  Period.  It can contain any sequence of characters, the encoding and interpretation of which is solely understood by the application that created it.  CVS should do nothing in terms of keyword expansion or End Of Line conversion to modify a binary

Re: Proposal to fix CVS binary file implementation

2000-12-21 Thread Paul Sander
I agree in principle with your statements and your proposal, but I observe two omissions: 1. There is a class of text file that is not mergeable, but requires newline conversion. CVS does not currently support that class of file, but I believe it should. Supporting that class of file would mean

Re: Proposal to fix CVS binary file implementation

2000-12-21 Thread David L. Martin
From: "Paul Sander" > I agree in principle with your statements and your proposal, but I observe > two omissions: > > 1. There is a class of text file that is not mergeable, but requires newline > conversion. CVS does not currently support that class of file, but I > believe it should. Supportin

Re: Proposal to fix CVS binary file implementation

2000-12-21 Thread Derek R. Price
Paul Sander wrote: > I agree in principle with your statements and your proposal, but I observe > two omissions: > > 1. There is a class of text file that is not mergeable, but requires newline > conversion. CVS does not currently support that class of file, but I > believe it should. Supportin

Re: Proposal to fix CVS binary file implementation

2000-12-28 Thread Greg A. Woods
[ On Thursday, December 21, 2000 at 00:22:41 (-0600), David L. Martin wrote: ] > Subject: Proposal to fix CVS binary file implementation > > A binary file is a binary file. Period. It can contain any sequence > of characters, the encoding and interpretation of which is solely >

Re: Proposal to fix CVS binary file implementation

2000-12-28 Thread David H. Thornley
"Greg A. Woods" wrote: > > [ On Thursday, December 21, 2000 at 00:22:41 (-0600), David L. Martin wrote: ] > > Subject: Proposal to fix CVS binary file implementation > > > > A binary file is a binary file. Period. It can contain any sequence > > of cha

Re: Proposal to fix CVS binary file implementation

2000-12-28 Thread Paul Sander
--- Forwarded mail from [EMAIL PROTECTED] (Greg Woods) >[ On Thursday, December 21, 2000 at 00:22:41 (-0600), David L. Martin wrote: ] >> Subject: Proposal to fix CVS binary file implementation >> >> If the user wants to change the "binary-ness" of a file, this s

Re: Proposal to fix CVS binary file implementation

2000-12-28 Thread David L. Martin
From: "Greg A. Woods" <[EMAIL PROTECTED]> > [ On Thursday, December 21, 2000 at 00:22:41 (-0600), David L. Martin wrote: ] > > Subject: Proposal to fix CVS binary file implementation "Proposal to improve CVS binary file implementation" would probably have

Re: Proposal to fix CVS binary file implementation

2000-12-29 Thread Derek R. Price
Paul Sander wrote: > --- Forwarded mail from [EMAIL PROTECTED] (Greg Woods) > >Think about it: You've got some changes you are about to commit that > >include changes to a file which you've tagged as un-mergable (i.e. it is > >a binary, opaque, file). As you run "cvs commit" you discover that >

Re: Proposal to fix CVS binary file implementation

2000-12-29 Thread Derek R. Price
"Derek R. Price" wrote: > There is the example of, say, GIF to JPEG. That could be considered mergable with > a proper tool. Perhaps *.doc and RTF is a better example. What an automated merge tool would do is more obvious. Derek -- Derek Price CVS Solutions Architect ( h

Re: Proposal to fix CVS binary file implementation

2000-12-29 Thread Noel L Yap
L PROTECTED], [EMAIL PROTECTED] cc: (bcc: Noel L Yap) Subject: Re: Proposal to fix CVS binary file implementation "Derek R. Price" wrote: > There is the example of, say, GIF to JPEG. That could be considered mergable with > a proper tool. Perhaps *.doc and RTF is a better example.

Re: Proposal to fix CVS binary file implementation

2000-12-30 Thread Paul Sander
>--- Forwarded mail from [EMAIL PROTECTED] >Paul Sander wrote: >> --- Forwarded mail from [EMAIL PROTECTED] (Greg Woods) >> >Think about it: You've got some changes you are about to commit that >> >include changes to a file which you've tagged as un-mergable (i.e. it is >> >a binary, opaque, fil

Re: Proposal to fix CVS binary file implementation

2001-01-03 Thread Derek R. Price
Paul Sander wrote: > >--- Forwarded mail from [EMAIL PROTECTED] > > >Paul Sander wrote: > > >> Oh yeah, there's that problem where different versions might contain > >> different types of data. Again, files containing different types of > >> data should have different version histories. Unfortu

Re: Proposal to fix CVS binary file implementation

2001-01-04 Thread Eric Siegerman
On Thu, Dec 28, 2000 at 03:22:36PM -0600, David H. Thornley wrote: > It could be worthwhile expanding the RCS > format to do some better handling of binary files. It would be > possible to improve the handling of binary files while keeping > most of the code base. The extension to the RCS format

Re: Proposal to fix CVS binary file implementation

2001-01-05 Thread Paul Sander
Eric has some good ideas. I wonder if we could get Paul Eggert to add support to RCS to directly fetch and set newphrases, in case someone needs them someday. However: --- Forwarded mail from [EMAIL PROTECTED] - One can imagine adding a per-revision attribute that says where in the sandb

Re: Proposal to fix CVS binary file implementation

2001-01-07 Thread Mark D. Baushke
On Fri, 5 Jan 2001 10:56:52 -0800, From: [EMAIL PROTECTED] (Paul Sander) wrote: > > Also CVS currently can't handle the case where a single sandbox directory > contains working copies of files collected from more than one directory in > the repository. The Entries file would have to be modified