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
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
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?
Great! This did fix the timeline.
I see harmless Edit event at top of the timline, which is expected.
Thanks for the quick support!!
- Original Message -
From: Richard Hipp
Sent: 07/25/12 05:40 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Fixing a bad time stamp
4 matches
Mail list logo
