Problems with linuxppc_2_4_devel

[Tom Rini]

On Tue, Jan 15, 2002 at 01:02:03PM -0800, Larry McVoy wrote:

> a) try and connect to a well known time server and see if the time is too
>    far off at commit time.  May or may not work.

This would require some external program tho, wouldn't it?

> b) see if the time is "too different" from the last changeset.  Most trees
>    are fairly active and if the time is too far ahead (say a month?), then
>    raise a warning and ask the user to confirm this is the correct time.

I'd say 'b' with an override option (yes, the clock IS fine, the tree
has just been dead for awhile).

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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