Problems with linuxppc_2_4_devel

[Gabriel Paubert]

On Tue, 15 Jan 2002, Larry McVoy wrote:

> What I was thinking was one of two approaches:
>
> 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.

While there are NTP servers all around the globe (and I maintain the one
we have here at work), finding the nearest one is not always easy.
Furthermore some people may create a changeset while disconnected on a
laptop or would object the cost of an additional call just to get the
time.


> 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.

Probably better, although I like the a) solution because it is likely to
be more exact. AFAIK the bk variables in the usr home directory only
affect the GUI Tools look and feel, it would be too much a stretch to add
a time server specification, no ?

	Regards,
	Gabriel.


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