CVS lock ?

[Vladimir Dergachev]

Well, it turns out the problem can be worked around by updating
ChangeLog and radeon_accel separately. I.e. the line

cvs -z3 ../../../../../../ChangeLog radeon_accel.c

complains about needing to update radeon_accel.c first,
however doing

cvs -z3 radeon_accel.c
cvs -z3 ../../../../../../ChangeLog

separately worked fine.

At the moment I suspect some weirdness with server-side scripts..

                          best

                            Vladimir Dergachev

On Thu, 16 Dec 2004, Daniel Stone wrote:

> On Thu, 2004-12-16 at 08:11 -0500, Vladimir Dergachev wrote:
>> volodya at silver:/nfs/node2-storage/Trees/xf86/X.org/xc/programs/Xserver/hw/xfree86/drivers/ati$
>> cvs -z3 update radeon_accel.c
>> M radeon_accel.c
>>
>> And the output of cvs -z3 status radeon_accel.c confirms I have an
>> up to date version:
>
> Wow, I have no idea, sorry.  Try starting from a clean tree (maybe a
> clean checkout), and moving your changes into place; sounds like CVS is
> horribly, horribly confused.
>