info-cvs
[Top][All Lists]
Advanced

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

Update from head gets an old revision


From: GraemeF
Subject: Update from head gets an old revision
Date: 8 Sep 2005 02:26:25 -0700
User-agent: G2/0.2

Hi,

We've been getting on quite nicely with CVS (CVSNT & TortoiseCVS on
Windows) for the last few months, but yesterday we ran into the
following problem. Our commits seem to be working fine, but any updates
from the HEAD are fetching an old revision. For example:

>cvs log Aston.Outputs.csproj
[snip!]
keyword substitution: t
total revisions: 25;    selected revisions: 25
description:
----------------------------
revision 1.25
date: 2005/09/07 15:27:50;  author: graeme.foster;  state: Exp;  lines:
+4 -0;  kopt: t;  commitid: c50431f06f50981;  filename:
Aston.Output.csproj;
Merge module for Aston.Output
----------------------------
revision 1.24
date: 2005/09/01 09:06:18;  author: graeme.foster;  state: Exp;  lines:
+15 -0;  kopt: t;  commitid: da44316c48910b1;  filename:
Aston.Output.csproj;
Made the output stuff look slicker
----------------------------
revision 1.23
date: 2005/08/03 15:07:36;  author: graeme.foster;  state: Exp;  lines:
+2 -0;  kopt: t;  commitid: a8042f0ddb74b5d;  filename:
Aston.Output.csproj;
Can now set line standard and anti alias level on outputs.
----------------------------
revision 1.22
date: 2005/08/02 10:37:25;  author: graeme.foster;  state: Exp;  lines:
+8 -1;  kopt: t;  commitid: 8c842ef4ce32e6e;  filename:
Aston.Output.csproj;
Got outputs working with TX
----------------------------
[snip!]

>cvs status Aston.Outputs.csproj
===================================================================
File: Aston.Output.csproj       Status: Up-to-date

   Working revision:    1.24
   Repository revision: 1.24
/labcvs/Helix/Aston.Output/Aston.Output.csproj,v
   Expansion option:    t
   Commit Identifier:   da44316c48910b1
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      -kt
   Merge From:          (none)


This is on a clean checkout of the module. As you can see, the latest
revision is 1.25, but the status says 1.24, and any updates or
checkouts (without specifying revision 1.25) get revision 1.24.

Any ideas? We're really stumped. My manager never wanted us to leave
SourceSafe and doesn't like CVS, so I'd really appreciate a response!
:)

Cheers,
G.



reply via email to

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