Re: binary files bad idea? why?

Hello, * On Thu, May 20, 2004 at 09:50:13AM -0400 Jim.Hyslop wrote: Spiro Trikaliotis wrote: This is no problem from my experience if the initial check-in was done from a Unix (LF-) based system, but it is a problem if it was done from a DOS (CR/LF-) based system. There is also a remote

RE: Special tag name for the tip of a branch

I believe THE branch name is the tag for the HEAD of a branch... -chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Taler Sent: Saturday, May 22, 2004 10:57 AM To: [EMAIL PROTECTED] Subject: Special tag name for the tip of a branch Hi

Re: Consistency check of repository knowing whether files are being watched

Hi Mark, The CVS/fileattr directory in the parent may list a foo,v file that is found in Attic/foo,v however, it should not be possible to have both a ./foo,v and an ./Attic/foo,v in the same tree, so the added expense is mostly in processing the CVS/fileattr files using a search path

Re: Consistency check of repository knowing whether files are

marko writes [quoting Mark?]: Shortly, on feature the 'cvs ls' or 'cvs rls' command will be useful to you... Otherwise, using something like a 'cvs log -r1' may be useful. Strange, my cvs 1.11.5 doesn't have a (r)ls command... He said on feature. 1.11 is the stable branch, 1.12 is

Error during merge

I'm merging branchY into branchX via cvs -nq update -j b_branchX -j b_branchY proj (I use the -nq so it does do the update yet ) and I get retrieving revision 1.2.4.2 retrieving revision 1.2 Merging differences between 1.2.4.2 and 1.2 into file1.cpp cvs update: file1.cpp: No such file

Commit ID Enhancement

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It occurred to me that a Commit ID implemented as a tag might make a useful addition to the CVS feature-set. If a unique commit id tag were applied to each revision as it is committed (unique across the repository and the same for each file in a

strongCVS Security Vulnerability/strong

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, For those who don't know, cvshome.org is currently down because it was hacked, via its CVS server we believe. cvshome.org was used to send an email that contains an exploit for the security vulnerabiliy CAN-2004-0396

FW: CVS update issue using -j to merge files between a branch and the trunk

This was sent by a co-worker of mine on May 6th. However for some reason it did not get to the mailing list. So I am sending this again. Hamid Ghassemi -Original Message- From: Joe Reifel ([EMAIL PROTECTED]) Sent: Thursday, May 06, 2004 12:21 PM To: '[EMAIL PROTECTED]' Subject: CVS

Re: Commit ID Enhancement

Derek Robert Price wrote: It occurred to me that a Commit ID implemented as a tag might make a useful addition to the CVS feature-set. From my perspective, only a minor improvement, as it only builds into cvs something that I can do as frequently or seldom as I (as the cm person on several

cvshome.org is offline?

I am not able to get to cvshome.org. Connection attempts timeout. Did I miss an outage announcement? Is there an alternative CVS download site? Alan ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs

Re: Commit ID Enhancement

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd Denniston wrote: Derek Robert Price wrote: It occurred to me that a Commit ID implemented as a tag might make a useful addition to the CVS feature-set. From my perspective, only a minor improvement, as it only builds into cvs something that I

Re: Error during merge

On Mon, May 24, 2004 at 03:52:56PM -0400, [EMAIL PROTECTED] wrote: I'm merging branchY into branchX via cvs -nq update -j b_branchX -j b_branchY proj (I use the -nq so it does do the update yet ) and I get retrieving revision 1.2.4.2 retrieving revision 1.2 Merging differences