[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bizarre update behaviour
From: |
James Hughes |
Subject: |
Bizarre update behaviour |
Date: |
Thu, 14 Mar 2002 12:07:15 -0500 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 |
Greetings:
First, a bit of Changelog to illustrate my problem:
2002-03-11 17:50 jhughes
* dps.pc (1.71): Added store_sig_repo message for use by fa
2002-03-06 16:22 jhughes
* dps.pc (1.70): New message: get_dispatch_list
2002-02-15 14:46 jhughes
* dps.pc (1.69): Fixed incorrect parameter bug in calls to
query_*() functions
My first problem is that the change in rev 1.69 has disappeared sometime
between 1.69 and 1.71. I've posted before about code getting clobbered
and basically been told it's human error, which I can buy, but still,
it's mystifying how 3 successive changes by the same developer result in
changes disappearing.
However, what's more mystifying is what happened when I tried to restore
the change that I had made in 1.69:
doing this
cvs up -r 1.69
resulted in 6 files with the message,
*.c is no longer in the repository
And not only that, but those same files had magically disappeared from
the working directory. Repeated updates and a fresh checkout over the
existing directory fail to pull them down again. However, creating a new
directory and doing a fresh 'cvs co' pulled everything down as expected.
Can anyone tell what I'm doing wrong?
tia
James
--
James Hughes
Esponsive Communications
613-549-3708 ext. 237
================================================================
What is design?...It's where you stand with a foot
in two worlds--the world of technology and the world of
people and human purposes--and you try to bring the two together.
Mitchell Kapor, A Software Design Manifesto
================================================================
- Bizarre update behaviour,
James Hughes <=