[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs commit: Up-to-date check failed

From: Donald Sharp
Subject: Re: cvs commit: Up-to-date check failed
Date: Wed, 1 Aug 2001 12:38:26 -0400
User-agent: Mutt/1.2.4i

When you get up to date failures, it means that the working
copy( in your sandbox ) is not based off of the latest
that is saved in the repository.  In this situation
you need to run a cvs update first and then resolve
any merge conflicts( if at all ) and then retry 
to commit.  

You really want the working copy to be up-to-date
before you commit, else you can have situations where
you commit a change and loose other changes that
people have made to the file in question.


On Wed, Aug 01, 2001 at 11:15:57AM -0500, berry wrote:
> Larry,
> We are switching from RCS to CVS
> at our company. I have received
> the cvs commit: Up-to-date check failed 
> abort several times when "playing"
> with CVS and I don't understand it.
> Can you provide an explanation of
> the reasons this abort occurs so that
> we know what is going on? Is there a
> way to do a commit without doing this
> check?
> Regards,
> David Berry
> Petroleum Geo-Services
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]