You can do fossil ui, select the checkin with wrong date and edit the date to approximate correct value.
- Altu -----Original Message----- From: Wilson, Ronald <[email protected]> To: [email protected] Sent: Thu, Jul 1, 2010 8:25 pm Subject: Re: [fossil-users] ancestor check-in is younger > I tried to do a commit on one of my repo's and I get this:> > Autosync: http://[email protected]:8080/rpw_sqlite> Bytes Cards Artifacts Deltas> Send: 130 1 0 0> Received: 1518 33 0 0> Total network traffic: 329 bytes sent, 998 bytes received> c:\rev\bin\fossil.exe: ancestor check-in [0c34a3248a] (2010-07-01> 14:38:11) is younger (clock skew?)> > So I check the webpage and the last checkin is dated 5695-09-24.> > How could that have happened and how can I fix it? This effectively> prevents me from committing any further changes.Sorry for the self reply, but here is some info:Fossil infoproject-name: <unnamed>repository: C:/rev/fossil/rpw.sqlite.fossillocal-root: C:/rev/src/rpw.sqlite/user-home: C:/Users/rwilso20/AppData/Localproject-code: 79331259170ac9c638ff1894f6e386eb2ac2ccf5server-code: d2abd35a8766649a0a2df295826798a7f042bc98checkout: 0c34a3248a6788e899ea0e24c843d693ec0f86a5 5695-09-2415:34:13 UTCparent: 123ba5968ff0f7a2c7a01b08de386a6d2fd50300 2010-06-0117:59:23 UTCtags: trunkfossil verThis is fossil version [ba14c7549c] 2010-06-26 20:37:08 UTCI'm not sure which version of fossil was used to make the offendingcommit in the year 5695. I stay pretty close to the latest devsnapshot. RWRon Wilson, Engineering Project Lead(o) 434.455.6453, (m) 434.851.1612, www.harris.comHARRIS CORPORATION | RF Communications Divisionassuredcommunications(tm)________________________________________ _______fossil-users mailing [email protected]http://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
