Re: Commit problem

[Paul Edwards]

"Nick" <saber850@yahoo.com> wrote in message 
pan.2003.12.24.13.43.13.147712@yahoo.com">news:pan.2003.12.24.13.43.13.147712@yahoo.com...
> > I think if you do this, you'll find the behaviour is identical.
> You're right.  I took some time today and reverted to 1.11.5; it yields
> the same results.
>
> I also tried creating a new, separate repository but it also behaves the
> same.
>
> I'm stumped at this point.  It doesn't seem to be CVS, nor does it seem to
> be my repository.
>
> I'd appreciate any suggestions or ideas.

You need to create a small test script that demonstrates the
problem, preferably set up to work on a Unix system.  That
way there is a at least a chance someone will run the script
on their system to see if they get the same behaviour.

E.g. take a look where I reported an integrity problem with
deleted files during a merge.

However, even if someone runs the script and reproduces
the problem, doesn't necessarily mean that the problem
will be fixed, just that it will be acknowledged.  That's
what happened with my report of code changes getting
lost during a merge operation anyway, which is a real
shame, because I was really hoping that this would be
fixed at the site where I installed CVS.

However, your problem sounds so fundamental, that by
the time you've finished writing the script, you will have
already figured out what the problem is.

CVS basically doesn't have fundamental problems.  The
fundamentals are secure.

BFN.  Paul.