linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Why these crazy timstamps on some ChangeSets ?
@ 2001-11-27 12:41 Gabriel Paubert
  2001-11-27 16:10 ` Larry McVoy
  0 siblings, 1 reply; 2+ messages in thread
From: Gabriel Paubert @ 2001-11-27 12:41 UTC (permalink / raw)
  To: linuxppc-dev


	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.


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Why these crazy timstamps on some ChangeSets ?
  2001-11-27 12:41 Why these crazy timstamps on some ChangeSets ? Gabriel Paubert
@ 2001-11-27 16:10 ` Larry McVoy
  0 siblings, 0 replies; 2+ messages in thread
From: Larry McVoy @ 2001-11-27 16:10 UTC (permalink / raw)
  To: Gabriel Paubert; +Cc: linuxppc-dev


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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-11-27 16:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-11-27 12:41 Why these crazy timstamps on some ChangeSets ? Gabriel Paubert
2001-11-27 16:10 ` Larry McVoy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).