On Wed, 07 May 2008 10:27:03 +0200, Peter Toft <[EMAIL PROTECTED]> wrote: > On Wed, 07 May 2008 09:21:56 +0200, Peter Toft <[EMAIL PROTECTED]> wrote: >> Hi all >> >> I like to draw your attention towards a nasty limitation to CVS locks, >> which >> I at least did not know until now. > > I forgot to mention that I have prior to the stuff below set > cvs watch on README.txt > > Best > > /peter
IMHO it is a design-flaw since I could easily be in a situation, where I like to signal that I am working on a certain file, i.e. I use cvs watch on + cvs edit but somebody asks me to export the module or test something where I need to check out the same module in parallel to the first checkout. I find this behaviour with CVS 1.12.13. Is there any way to avoid this clearing of file locks? Best Peter > >> >> $ cvs checkout my_proj >> ... lots of check out lines... >> $ cd my_proj >> $ cvs editors # No files will be shown since no files are >> locked >> $ cvs edit README.txt >> $ cvs editors . >> README.txt pto Wed May 7 06:43:15 2008 -0000 myworkstation > > >> >> /opt/cvsroot/my_proj >> $ cd .. >> $ mv my_proj my_proj_work >> $ cvs checkout -r HEAD my_proj >> $ ls -1d >> my_proj >> my_proj_work >> $ cd my_proj_work >> $ cvs editors . >> >> Bummer - the lock on my_proj/README.txt is gone.... :-(( >> Pure magic - but very annoying magic.... >> >> How come? Can I make some different operation, where I don't loose the >> file >> lock. >> >> Note; If I replace the second "cvs checkout" with "cvs export" I have > the >> same problem. >> >> >> Best >> >> Peter Toft, Ph.D. [EMAIL PROTECTED] http://petertoft.dk >> >> >> >> _______________________________________________ >> Bug-cvs mailing list >> [email protected] >> http://lists.nongnu.org/mailman/listinfo/bug-cvs > -- Peter Toft, Ph.D. [EMAIL PROTECTED] http://petertoft.dk Følg min Linux-blog på http://www.version2.dk/blogs/petertoft _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
