[Top][All Lists]

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

Re: Up-to-date check failed for 'module'

From: David Berry
Subject: Re: Up-to-date check failed for 'module'
Date: Thu, 21 Jun 2001 13:37:57 -0500


Thanks for your quick response. We have had
the situation in the past where a developer
checks out a source set, makes some really bad
changes and then checks it back into RCS,
soon to be CVS. We in maintenance are charged
with the task of fixing these blunders in the
latest revision. Suppose I check out the source
prior to the screw up, make fixes and try to check
it in on top of the bad version. I get up-to-date
check failures! What am I to do? Create a branch,
or remove the bad version? I can see we are going
to have some problems using CVS! Our developers are
not disciplined enough to not check in BAD code.

David Berry

Larry Jones wrote:
> David Berry writes:
> >
> > I have versions 201.4, 201.5 and 201.6 .
> > There is NO difference in the code in
> > any of these versions, except for the
> > revision string $Id:$
> Note that a difference is a difference; the fact that it's in the
> revision string doesn't really matter.
> > When I check out 201.4 and try to check
> > it back in on top of 201.6, I get the
> > following:
> > cvs commit: Up-to-date check failed for `alnmo.c'
> > cvs [commit aborted]: correct above errors first!
> What this is telling you is that there is a more recent revision of that
> file in the repository.  If you were to check in your current copy of
> the file, you would lose the changes from the more recent revision(s) in
> the repository, so CVS won't allow it.  You need to use ``cvs update''
> (perhaps with the -A option) to update your working copy to the most
> recent revision in the repository before CVS will allow you to check it
> in.
> -Larry Jones
> Why is it you always rip your pants on the day everyone has to
> demonstrate a math problem at the chalkboard? -- Calvin

reply via email to

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