Fourth draft of the Y2038 design document

[Albert ARIBAUD]

Hi all,

I have produced a fourth draft of what will eventually become the Y2038
design document:

https://sourceware.org/glibc/wiki/Y2038ProofnessDesign?rev=83

Relative to the previous draft:

 * the scope clarifies that *only* Y2038 is considered, and no other
   doomsday such as Y2106 or Y9999;

 * all types directly or indirectly derived from time_t are now listed;

 * all APIs using these types are now listed;

 * all functions which use time_t internally are now listed;

 * also listed are types and APIs related to time but which are
   Y2038-safe (even though they might be unsafe for some other
   doomsday, e.g. struct rpc_timeval being Y2106-unsafe).

As always, comments welcome.

Cordialement,
Albert ARIBAUD
3ADEV