I think that's an option... However, I found that the rid is referred by few more files:
$ grep -R 175ba5364e06838d022133fffe20986aab57c2e7 * 0e/54f21fbf35f5f9e6ac9f7c9a4070cce05aa8d3:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-30T03:57:00 49/b000689b4b2cc1970a7bb71022da00debc421d:T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 c1/4bf45b61b68c4e5f27f061c5baedfe0f8d7a58:P 175ba5364e06838d022133fffe20986aab57c2e7 f3/1a2c3f5098596e9137aec147bb20753c401530:M 175ba5364e06838d022133fffe20986aab57c2e7 First two are my attempts to change the commit dates but later two bother me. I'm worried I'll end up modifying all commits since the bad one or fossil will report integrity issues. ----- Original Message ----- From: Lluís Batlle i Rossell Sent: 07/25/12 01:07 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Fixing a bad time stamp that is in future On Wed, Jul 25, 2012 at 12:35:14AM -0400, Altu Faltu wrote: > This doesn't happen on every new repo - only on fresh checkouts of the repo where I have this problem. Well, I think there is always the option to dump the fossil to artifact files, edit the artifact contents, recalculate shasums, and compose back the repository. :) > ----- Original Message ----- > From: Stephan Beal > Sent: 07/24/12 08:42 PM > To: Fossil SCM user's discussion > Subject: Re: [fossil-users] Fixing a bad time stamp that is in future > > If this happens on every new repo then something is fundamentally broken on your machine. In 4 years of using fossil every day this has never happened yo me. > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > On Jul 24, 2012 12:35 PM, "Altu Faltu" < altufa...@mail.com > wrote: > My system must have been in a bad state when that happened. I realised it much later when a fresh checkout did not give me latest versions. > > I have a workaround that I use for every fresh checkout, but a fix would be good and I can wait for it. > > ----- Original Message ----- > From: Richard Hipp > Sent: 07/24/12 03:50 PM > To: Fossil SCM user's discussion > Subject: Re: [fossil-users] Fixing a bad time stamp that is in future > > > On Tue, Jul 24, 2012 at 1:17 AM, Altu Faltu < altufa...@mail.com > wrote: > One of my repository has got a bad time stamp on a commit such that the commit date is in future. Since commit date is in future, any attempts to edit the commit doesn't take effect. > > Is there any way to fix this issue? > Wow. How did that happen??? > > I don't have a good way to fix this at the moment. But I'll try to think of something.... > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > -- > D. Richard Hipp > d...@sqlite.org > > ________________________________ _______________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
