--- Forwarded mail from Greg Woods:
[ On Friday, July 2, 2004 at 12:49:58 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
--- Forwarded mail from [EMAIL PROTECTED]
[ On Wednesday, June 30, 2004 at 22:59:27 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts
[ On Friday, July 2, 2004 at 12:49:58 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
--- Forwarded mail from [EMAIL PROTECTED]
[ On Wednesday, June 30, 2004 at 22:59:27 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
(A) they're
[ On Thursday, July 1, 2004 at 14:33:11 (-0700), Paul Sander wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
What are you talking about? I can think of only two ways that CVS
uses the deltas:
Well, as usual you got off on the wrong track right from the start
again
--- Forwarded mail from [EMAIL PROTECTED]
[ On Wednesday, June 30, 2004 at 22:59:27 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
(A) they're not sources -- they're intermediate product files.
They're not intermediate product files unless they can be reproduced
--- Forwarded mail from [EMAIL PROTECTED]
[ On Monday, June 28, 2004 at 18:31:58 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
On three separate occasions, Greg actually *recommends* intalling and
treating such code drops as uncontrolled sources!
Paul, please stop
--- Forwarded mail from [EMAIL PROTECTED]
[ On Monday, June 28, 2004 at 19:02:19 (-0700), Paul Sander wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
I have never, ever advocated changing the format of an RCS file in a
way that would break the ci, co, rcs, or rlog
--- Forwarded mail from [EMAIL PROTECTED]
[ On Monday, June 28, 2004 at 14:58:03 (-0700), Mark D. Baushke wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
Yes, but diff is not diff3. diff is used for the
delta format. diff3 is used by rcsmerge, not for
fundamental
[ On Monday, June 28, 2004 at 19:02:19 (-0700), Paul Sander wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
I have never, ever advocated changing the format of an RCS file in a
way that would break the ci, co, rcs, or rlog programs. And although
I strongly advocate
[ On Tuesday, June 29, 2004 at 02:18:26 (-0700), Paul Sander wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
I.e. How do you propose to make it possible for the standard RCS tools
alone to re-create _every_ revision from all files created by this
hacked system
[ On Monday, June 28, 2004 at 14:58:03 (-0700), Mark D. Baushke wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
Yes, but diff is not diff3. diff is used for the
delta format. diff3 is used by rcsmerge, not for
fundamental version deltas.
I think you're confused
[ On Tuesday, June 29, 2004 at 19:34:25 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
When you speak about how great NASA is and mention the antiquity of some
of their processes, remember that the paper checklists have since
contributed to the failure of several
--- Forwarded mail from [EMAIL PROTECTED]
Mark, I agree with your response to Greg's claims about RCS
compatibility, or the lack thereof.
In particular, I am not aware of any fundamental
problems rcs 5.7 will have if someone were to
introduce a new keyword which would name a program
other than
--- Forwarded mail from [EMAIL PROTECTED]
[ On Monday, June 28, 2004 at 01:44:36 (-0700), Mark D. Baushke wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
The RCS format is very extensible and in fact the
CVSNT folks have extended it already and I have had
no problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander [EMAIL PROTECTED] writes:
--- Forwarded mail from [EMAIL PROTECTED]
Rather than use a hint to expose an
implementation detail, I suggest recording a
data type instead. Maybe even a MIME type. Then
provide a suitable mechanism to
--- Forwarded mail from [EMAIL PROTECTED]
Paul Sander [EMAIL PROTECTED] writes:
--- Forwarded mail from [EMAIL PROTECTED]
=20
Rather than use a hint to expose an
implementation detail, I suggest recording a
data type instead. Maybe even a MIME type. Then
provide a suitable mechanism to map
--- Forwarded mail from [EMAIL PROTECTED]
[ On Monday, June 28, 2004 at 11:00:23 (-0400), Jim.Hyslop wrote: ]
Subject: RE: CVS corrupts binary files ...
Any manual procedure is prone to error. I prefer to automate things as much
as possible, to minimize the possibility of human error. Any
Greg A. Woods wrote:
While I agree with most of what you wrote, I'd like to examine this one a
little more:
Also what you and many other folks seem to forget as well is
that manual procedures and processes can be far easier and
more effective than canned software tools for implementing
[ On Monday, June 28, 2004 at 01:44:36 (-0700), Mark D. Baushke wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
The RCS format is very extensible and in fact the
CVSNT folks have extended it already and I have had
no problems using CVSNT repositories in conjunction
[ On Monday, June 28, 2004 at 11:00:23 (-0400), Jim.Hyslop wrote: ]
Subject: RE: CVS corrupts binary files ...
Any manual procedure is prone to error. I prefer to automate things as much
as possible, to minimize the possibility of human error. Any time I see a
manual process, I wonder how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods [EMAIL PROTECTED] writes:
[ On Monday, June 28, 2004 at 01:44:36 (-0700), Mark D. Baushke wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
The RCS format is very extensible and in fact the
CVSNT folks
--- Forwarded mail from [EMAIL PROTECTED]
[ On Thursday, June 17, 2004 at 15:49:39 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
Nope, I got it. The thing is, you can control pointers (e.g. makefiles
containing references to files stored in a library somewhere) all
--- Forwarded mail from Greg Woods:
[ On Thursday, June 17, 2004 at 16:49:42 (-0700), Paul Sander wrote: ]
Subject: Smoke, FUD (was Re: CVS corrupts binary files ...)
If this is true, then we're in violent agreement. But to date, you have
argued that making the necessary changes to CVS
--- Lars [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
--- Mark D. Baushke [EMAIL PROTECTED] wrote:
Checking in binary files is not encouraged for cvs
use.
Well what can I do ? It happends that my project
(a
web site) includes binary files...
Here is a list
[ On Tuesday, June 8, 2004 at 15:01:10 (-0700), Adrian Constantin wrote: ]
Subject: Re: CVS corrupts binary files ...
--- Greg A. Woods [EMAIL PROTECTED] wrote:
[ On Saturday, June 5, 2004 at 13:01:48 (-0700),
Adrian Constantin wrote: ]
Subject: Re: CVS corrupts binary files
[ On Wednesday, June 9, 2004 at 09:15:24 (-0400), Jim.Hyslop wrote: ]
Subject: RE: CVS corrupts binary files ...
Let's not throw the baby out with the bathwater, shall we? Granted, CVS was
not *originally* designed to handle binary files. Granted, CVS does not
handle binary files as well
[ On Wednesday, June 9, 2004 at 09:35:37 (-0400), Tom Copeland wrote: ]
Subject: Re: CVS corrupts binary files ...
On Tue, 2004-06-08 at 17:42, Paul Sander wrote:
Keep in mind also that there's a difference between binary files and
mergeable files.
That's a neat point.
Well, it's kind
On Thu, 2004-06-17 at 16:12, Greg A. Woods wrote:
Most of my Java projects use 3rd party jar files,
which are compressed tar balls, more or less. And I certainly don't
want to try to merge foolib-0.1.jar with foolib-0.2.jar when a new
version comes out; I just want to put it in CVS so
--- Forwarded mail from [EMAIL PROTECTED]
[ On Tuesday, June 8, 2004 at 16:21:03 (-0700), Mark D. Baushke wrote: ]
Subject: Re: CVS corrupts binary files ...
It may be that the diff3 algorithm is not always
the best one suited to do such mergers.
That may be true, but the use
--- Forwarded mail from [EMAIL PROTECTED]
[ On Wednesday, June 9, 2004 at 09:15:24 (-0400), Jim.Hyslop wrote: ]
Subject: RE: CVS corrupts binary files ...
Let's not throw the baby out with the bathwater, shall we? Granted, CVS was
not *originally* designed to handle binary files. Granted
At 4:02 PM -0400 6/17/04, Greg A. Woods wrote:
People just need to learn to use the right tool for the job and to quit
being so bloody narrow minded when it comes to learning about new tools.
First, I do not claim to have anything resembling expert (or even
mediocre) knowledge in the usage of CVS
--- Forwarded mail from [EMAIL PROTECTED]
At 4:02 PM -0400 6/17/04, Greg A. Woods wrote:
I have no problem using/learning new tools. I'd personally love to be
able to use VooDoo for version control, but there are two problems:
1. It's not free
2. There is no standalone client for it
3. There
Greg A. Woods wrote:
[ On Wednesday, June 9, 2004 at 09:15:24 (-0400), Jim.Hyslop wrote: ]
Subject: RE: CVS corrupts binary files ...
Let's not throw the baby out with the bathwater, shall we? Granted,
CVS was not *originally* designed to handle binary files.
Granted, CVS
does
At 1:40 PM -0700 6/17/04, Paul Sander wrote:
Why would it not work well to use a CVS Wrapper to binhex (uuencode,
etc.) a binary file and then essentially have CVS to only see your
file as a text file?
The key is that there's a distinction between text files and mergeable
files. Programs like
[ On Thursday, June 17, 2004 at 16:25:02 (-0400), Tom Copeland wrote: ]
Subject: Re: CVS corrupts binary files ...
Hm. Why not simply check these jar files into the repository where they
can be tagged/branched/exported and so forth? Why should every
programmer on my team need to get all
[ On Thursday, June 17, 2004 at 13:06:44 (-0700), Paul Sander wrote: ]
Subject: Re: CVS corrupts binary files ...
Current releases of CVS do the latter. (Don't believe me? Look at
the function named RCS_merge in the rcscmds.c source file.) It's a
simple matter to replace the invocation
[ On Thursday, June 17, 2004 at 13:09:09 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
I've done revision control by backup, and I've done revision control
by naming convention. Both have proven to be disasters.
Obviously you tried to use these tehniques
[ On Thursday, June 17, 2004 at 17:03:34 (-0400), Eric Gorr wrote: ]
Subject: Re: CVS corrupts binary files ...
#1 is, of course, a very compelling reason to use any piece of
software that works. Can you point to an alternative to CVS that is
also free?
Check the various FAQs related
--- Forwarded mail from [EMAIL PROTECTED]
At 1:40 PM -0700 6/17/04, Paul Sander wrote:
Why would it not work well to use a CVS Wrapper to binhex (uuencode,
etc.) a binary file and then essentially have CVS to only see your
file as a text file?
The key is that there's a distinction between text
at 06:16:32PM -0400, Greg A. Woods wrote:
[ On Thursday, June 17, 2004 at 16:25:02 (-0400), Tom Copeland wrote: ]
Subject: Re: CVS corrupts binary files ...
Hm. Why not simply check these jar files into the repository where they
can be tagged/branched/exported and so forth? Why should every
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Gorr [EMAIL PROTECTED] writes:
Can you point to an alternative to CVS that is also free?
Certainly. There are a number of such programs.
Here are the Open Source and/or Free Software Source or configuration
management programs:
Aegis
Whew, the smoke's getting thick in here!
From: [EMAIL PROTECTED]
[ On Thursday, June 17, 2004 at 13:06:44 (-0700), Paul Sander wrote: ]
Subject: Re: CVS corrupts binary files ...
Current releases of CVS do the latter. (Don't believe me? Look at
the function named RCS_merge in the rcscmds.c
Greg A. Woods wrote:
[ On Saturday, June 5, 2004 at 13:01:48 (-0700), Adrian
Constantin wrote: ]
Subject: Re: CVS corrupts binary files ...
I don't wanna merge binary files, and I'm not likely to
modify them in
my module (project). I just want cvs to carry them along
[ On Saturday, June 5, 2004 at 17:10:58 (-0700), Paul Sander wrote: ]
Subject: Re: CVS corrupts binary files ...
Source files are any files that cannot
be reproduced automatically.
Nope, that's wrong too.
Source files are those files written and edited by humans.
Source _code_ is human
[ On Saturday, June 5, 2004 at 20:52:06 (-0700), Paul Sander wrote: ]
Subject: Re: CVS corrupts binary files ...
Yeah, well, sending such hapless people away is easier
than fixing the tool.
The tool is not broken -- I.e. there's nothing to fix!
CVS is designed _only_ for tracking changes
[ On Saturday, June 5, 2004 at 13:01:48 (-0700), Adrian Constantin wrote: ]
Subject: Re: CVS corrupts binary files ...
I don't wanna merge binary files, and I'm not likely
to modify them in my module (project). I just want cvs
to carry them along with the sources
Then your better tool
--- Forwarded mail from [EMAIL PROTECTED]
Source files are any files that cannot
be reproduced automatically.
Nope, that's wrong too.
Source files are those files written and edited by humans.
That's exactly what I said. Read that sentence again.
Source _code_ is human (and machine)
Oops, I omitted the Sept. 16 patch. Here it is at the bottom.
--- Forwarded mail from [EMAIL PROTECTED]
--- Forwarded mail from [EMAIL PROTECTED]
[ On Saturday, June 5, 2004 at 20:52:06 (-0700), Paul Sander wrote: ]
Subject: Re: CVS corrupts binary files ...
Yeah, well, sending such hapless
--- Greg A. Woods [EMAIL PROTECTED] wrote:
[ On Saturday, June 5, 2004 at 13:01:48 (-0700),
Adrian Constantin wrote: ]
Subject: Re: CVS corrupts binary files ...
I don't wanna merge binary files,
Then your better tool is called a directory (i.e.
outside of CVS)
--
You can't
--- Forwarded mail from [EMAIL PROTECTED]
[ On Saturday, June 5, 2004 at 20:52:06 (-0700), Paul Sander wrote: ]
Subject: Re: CVS corrupts binary files ...
Yeah, well, sending such hapless people away is easier
than fixing the tool.
The tool is not broken -- I.e. there's nothing to fix!
CVS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
Greg writes:
CVS is designed _only_ for tracking changes in
human written text files.
Paul writes:
Keep in mind also that there's a difference
between binary files and mergeable files.
The two concepts are in fact orthogonal; there
--- Forwarded mail from [EMAIL PROTECTED]
Greg writes:
CVS is designed _only_ for tracking changes in
human written text files.
Paul writes:
Keep in mind also that there's a difference
between binary files and mergeable files.
The two concepts are in fact orthogonal; there
are mergeable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gianni Mariani [EMAIL PROTECTED] writes:
Mark D. Baushke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
...
If someone wanted to hack in an automagical
recognition system that could
Mark D. Baushke writes:
If someone wants to write a patch that will run the
equivalent of 'file' on new source files to determine that
the file needs -kb by default, that would be a useful
extension to cvs client mode for both 'cvs add' and 'cvs
import' cases.
Note carefully that Mark said
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
Doug Lee [EMAIL PROTECTED] writes:
Is it a proven thing that CVS can corrupt a
binary file if no merges are tried and no
CR/LF boundary rules are broken?
No.
I got it.
It will
Hello,
* On Sat, Jun 05, 2004 at 08:38:15PM -0700 Gianni Mariani wrote:
*
Peter Connolly wrote:
Too dificult to set up, I think Shouldn't cvs have a list of binary
file types preinstalled in the cvswrappers ?
I agree, it should.
I second that ! I did 3 years ago.
Spiro Trikaliotis wrote:
Hello,
Hi !
...
If you have so much fear about binary files, why don't you put * -kb
into your cvswrappers, and declare any text file explicitly? This way,
you cannot miss the binary files.
Actually, that was suggested 3 years ago as well. It turns out to be a
very
Mark D. Baushke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
...
If someone wanted to hack in an automagical
recognition system that could be enabled for
binary file types, I suppose we could consider
adding it.
It already exists, it's
--- Forwarded mail from [EMAIL PROTECTED]
* On Sat, Jun 05, 2004 at 08:38:15PM -0700 Gianni Mariani wrote:
*
Peter Connolly wrote:
Too dificult to set up, I think Shouldn't cvs have a list of binary
file types preinstalled in the cvswrappers ?
I agree, it should.
I second that ! I did
Hi all,
I've created a simple repository on a Linux server
with one module wich is a web site. My working
directory is on a Windows machine and I have to use
ssh to connect to the server. I've tried several ssh
clients and with all of them the checkout command
creates corrupted image files in my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
I've created a simple repository on a Linux server
with one module wich is a web site. My working
directory is on a Windows machine and I have to use
ssh to connect to the server. I've tried several ssh
, 2004 11:45 PM
To: Adrian Constantin
Cc: [EMAIL PROTECTED]
Subject: Re: CVS corrupts binary files ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
I've created a simple repository on a Linux server
with one module wich is a web site. My
--- Peter Connolly [EMAIL PROTECTED] wrote:
And to make the -kb automatic with binary file
types, modify your
cvswrappers file...
Must I tell explicitly to cvs that I transfer
text/binary files between different systems ?
Yes, for binary files. See the -kb switch.
Or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
--- Peter Connolly [EMAIL PROTECTED] wrote:
And to make the -kb automatic with binary file
types, modify your
cvswrappers file...
Must I tell explicitly to cvs that I
transfer
--- Mark D. Baushke [EMAIL PROTECTED] wrote:
Adrian Constantin [EMAIL PROTECTED]
writes:
After hours of tests I got it to work.
For the begining...
Too dificult to set up, I think
You may wish to choose a tool that is better for
your particular needs. cvs is not at that friendly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Constantin [EMAIL PROTECTED] writes:
--- Mark D. Baushke [EMAIL PROTECTED] wrote:
Adrian Constantin [EMAIL PROTECTED]
writes:
After hours of tests I got it to work.
For the begining...
Too dificult to set up, I think
Too dificult to set up, I think
Shouldn't cvs have a list of binary file types
preinstalled in the cvswrappers ?
I agree, it should.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
You may wish to choose a tool that is better for
your particular needs. cvs is not at that friendly
at controlling and merging binary files.
Actually, if there are a lot of binary files in your repository, you might
want to consider switching to Subversion (http://subversion.tigris.org/)
since
Too dificult to set up, I think
Shouldn't cvs have a list of binary file types
preinstalled in the cvswrappers ?
I agree, it should.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
You may wish to choose a tool that is better for
your particular needs. cvs is not at that friendly
at controlling and merging binary files.
Actually, if there are a lot of binary files in your repository, you might
want to consider switching to Subversion (http://subversion.tigris.org/)
since
Adrian Constantin writes:
Or maybe projects for Unix/Linux platforms do not
usualy have binary files, but I don't really think so...
CVS is a *source* control system; source files are rarely binary. It
does support them as an afterthought, but that's not what it was
designed to do.
-Larry
--- Forwarded mail from [EMAIL PROTECTED]
Adrian Constantin writes:
Or maybe projects for Unix/Linux platforms do not
usualy have binary files, but I don't really think so...
CVS is a *source* control system; source files are rarely binary.
I disagree with this statement. Source files are
Is it a proven thing that CVS can corrupt a binary file if no merges
are tried and no CR/LF boundary rules are broken? In other words, if
I set -kb on a binary file and then do nothing to it but commit
updates and sometimes request an old revision, keeping my sandbox in
the OS in which it was
--- Paul Sander [EMAIL PROTECTED] wrote:
Adrian Constantin writes:
Or maybe projects for Unix/Linux platforms do not
usualy have binary files, but I don't really
think so...
CVS is a *source* control system; source files are
rarely binary.
I disagree with this statement. Source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Lee [EMAIL PROTECTED] writes:
Is it a proven thing that CVS can corrupt a binary file if
no merges are tried and no CR/LF boundary rules are
broken?
No.
In other words, if I set -kb on a binary file and then do
nothing to it but commit
Doug Lee [EMAIL PROTECTED] writes:
Is it a proven thing that CVS can corrupt a binary
file if
no merges are tried and no CR/LF boundary rules
are
broken?
No.
I got it.
It will corrupt my files in the default
configuration after instalation, until I tell it
that .gif files
--- Forwarded mail from [EMAIL PROTECTED]
Is it a proven thing that CVS can corrupt a binary file if no merges
are tried and no CR/LF boundary rules are broken? In other words, if
I set -kb on a binary file and then do nothing to it but commit
updates and sometimes request an old revision,
Peter Connolly wrote:
Too dificult to set up, I think
Shouldn't cvs have a list of binary file types
preinstalled in the cvswrappers ?
I agree, it should.
I second that ! I did 3 years ago.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg09098.html
BTW - the cvswrappers file in the
--- Forwarded mail from [EMAIL PROTECTED]
Doug Lee [EMAIL PROTECTED] writes:
In other words, if I set -kb on a binary file and then do
nothing to it but commit updates and sometimes request an
old revision, keeping my sandbox in the OS in which it was
checked out, could I ever get a bad
--- Forwarded mail from [EMAIL PROTECTED]
Doug Lee [EMAIL PROTECTED] writes:
I think there are some binary diff algorithms...
Indeed. Consider svn which uses xdelta internally.
To be fair, CvsNt also has ways of dealing better
with binary formats than the cvshome version.
There is
79 matches
Mail list logo
