RE: Mysterious reappearing files

"Adam Jack" <[email protected]>
Newsgroups gmane.comp.krysalis.sandbox
Message-ID <002b01c2d2a4$7853c2e0$f2d9ea43@wdn086>
Is CVS sick, or were it/I just out of synch?

	  cvs diff: [06:35:11] obtained lock in
/cvsroot/metamorphosis/krysalis-version
	failed due to an internal error (took 2:00.663)

-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of
Adam Jack
Sent: Wednesday, February 12, 2003 7:01 AM
To: [email protected]
Subject: Mysterious reappearing files


I keep getting "updates" from CVS on files I've relocated or deleted. They
just don't want to go away. ;-)

Is this user error? Is it 'cos folks are not religiously updating from the
repository before synchronizing? Is Eclipse making it too easy on us, and
allow us to make this mistake? Any good behaviours folks could demonstrate
to avoid this?

Also, I have a problem with .cvsignore --- I don't know how to keep
directory trees from getting checked in. I created a 'transient' for
generating test code into, and added it to the .cvsignore but still I see it
in. I read the .cvsignore only works at one level, but since we generate
code in a package hierarchy we need to go deep. Do I really need to put a
.cvsignore at every level?

I'll download the undead & re-delete.

regards

Adam
--
<http://www.TrySybase.com>
Experience Sybase Technology ...



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Krysalis-sandbox-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/krysalis-sandbox-dev



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.