On Wed, Jul 27, 2011 at 10:21 PM, Altu Faltu <altufa...@mail.com> wrote:
> Hi, > > Some help / pointers here will be useful.... > > I looked at timeline (UI) of one of my projects today and found a commit > with a future date, resulting in an N shape in timeline graph. I tried > updating the commit date using web interface but the graph did not change. > Looking at the commit information again, it says following under Overview: > > Date: 5695-09-30 21:53:28 > Received From: a0756885 @ on 5695-09-30 21:53:28 > This date can be corrected. But the rule is, the oldest record wins. So the "edit" that fixes this date must occur after 5695-09-30. It is clearly impractical to wait that long. But at this point in time, there is not a easy way that I know of to override the date for an "edit" record. I'll have to work on that. How badly is your system clock broken in order to get such a date? > > However, it says following under Tags and Properties: > > date=2010-06-23 16:53:28 added by [7396a17ae0] on 5695-09-30 22:06:36 > > It looks like I already tried to fix it in past. Any attempt to change the > commit date (I tried changing it to 2010-06-24 21:53:28 using 'edit' link) > does not take effect and commit information always shows above values. > > When I click [7396a17ae0] link, I get: > > Control artifact. > > > D 5695-09-30T22:06:36 > T +date 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 > U a0756885 > > > Z 78cd9d21c70bd742573d4c09577cc20d > > I did fossil rebuild and changing date again through web interface with > fossil version 1.18 [df9da91ba8], but it did not help. > > Is there a limit on how many times a commit date can be edited? > How do I fix this one? > > I did deconstruct in a temp folder and searched for files containing "+date", > which shows many files, relating to various attempts I made to correct it: > > > > $ grep -R "+date " * > > 1d/31959a78f56dfab7f7008c409e306e50c548fe:T +date > 2c585f0435a3cb128032442d6bd7ff75dfad3864 2010-01-07\s04:48:16 > 1d/cc744d2aa2a46567721bd9e03db07d5aef7fba:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 > 5c/011a1e3ac40f570c05f21a23ac07f0cd4015f1:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 > 6b/46affaa42c5014baf8a96ae82d592e9f82e347:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 > 73/96a17ae080a920f9287544f0e48472488bbbc8:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s16:53:28 > 8c/a6666b10e029c16fb93283c3849e06552276a2:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-24\s21:53:28 > a9/bb299a9e185f8532ebf12fe7664bb12eac4112:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2010-06-23\s21:53:28 > d8/84e3ccb48e5e214ab28592a86b077d5c0a5052:T +date > 175ba5364e06838d022133fffe20986aab57c2e7 2012-09-30\s21:53:28 > New repository after reconstruct shows same issue. - Altu > > _______________________________________________ > 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
