Why these crazy timstamps on some ChangeSets ?

Larry McVoy lm at bitmover.com
Wed Nov 28 03:10:07 EST 2001

It means that someone had screwed up clocks.  There isn't much we can do
about it, we need increasing dates.

On Tue, Nov 27, 2001 at 01:41:19PM +0100, Gabriel Paubert wrote:
> 	Hi,
> I just noticed that Changeset 1.678 and 1.679 on linuxppc_2_4_devel and
> 1.483 on linuxppc_2_4 have a date of February 23rd 2002.
> Quite annoying when browsing, because bk revtool displays all changes
> since these commits on the same date. I strongly suspect that this will
> last for 3 months or so, resulting in several hundred ChangeSets on the
> same day. I use latest stable bk version BTW.
> I suspect that there is no simple way of fixing this, bk won't like any
> fiddling with timestamps to make them more realistic. There may be a
> complex way, based on bk undo and reapplying all the patches (changing the
> date, user name and host name on the machine so that all patches get more
> or less the right values, but it does not look easy).
> 	Gabriel.

Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

More information about the Linuxppc-dev mailing list