Karl Berry asked:
> The ChangeLog file is over a megabyte now, and I'm still stuck on dialup
> sometimes. Can we split it to, say, ChangeLog.1997-2006 and just keep
> 2007 in the active file?
I believe that the size of the ChangeLog becomes insignificant once we switch
to 'git' as primary version
The ChangeLog file is over a megabyte now, and I'm still stuck on dialup
sometimes. Can we split it to, say, ChangeLog.1997-2006 and just keep
2007 in the active file?
Thanks,
k
Sergey Poznyakoff wrote:
> I propose the following change to sysexit_.h. Reason: if HAVE_SYSEXITS_H
> is expanded to 1, then the included header file might be protected by
> `#ifdef _SYSEXITS_H' (in fact, it is, on GNU/Linux) which will prevent
> its contents from being included.
Well spotted. Man
Geoff Clare <[EMAIL PROTECTED]> writes:
> Paul Eggert <[EMAIL PROTECTED]> wrote, on 30 Mar 2007:
>>
> Picky, picky. Let me restate it as "if the code ... outputs
> "SSIZE_MAX wrong" (through normal execution, not undefined behaviour),
Fine, but the point is that there's no portable way for an ap
Geoff Clare wrote:
The code was just to illustrate the point that if it is possible for
the condition (var > SSIZE_MAX) to be true then the implementation
does not conform to the requirement that SSIZE_MAX is the maximum
value of an object of type ssize_t.
I still don't buy that. If that was th
Paul Eggert <[EMAIL PROTECTED]> wrote, on 30 Mar 2007:
>
> Geoff Clare writes:
>
> > If the following code:
> >
> >ssize_t var;
> >var = SSIZE_MAX;
> >++var;
> >if (var > SSIZE_MAX)
> > puts("SSIZE_MAX wrong");
> >
> > outputs "SSIZE_MAX wrong" on any implementation, then var i
Geoff Clare writes:
> If the following code:
>
>ssize_t var;
>var = SSIZE_MAX;
>++var;
>if (var > SSIZE_MAX)
> puts("SSIZE_MAX wrong");
>
> outputs "SSIZE_MAX wrong" on any implementation, then var is an object
> of type ssize_t which was able to contain a value greater than
Paul Eggert <[EMAIL PROTECTED]> wrote, on 29 Mar 2007:
>
> My vague recollection is that ssize_t and SSIZE_MAX were put in
> precisely to support screwy implementations like Tandem. But
> this was a while ago and I wasn't there, so I could well be wrong.
The ssize_t type was introduced (in 1990)
I propose the following change to sysexit_.h. Reason: if HAVE_SYSEXITS_H
is expanded to 1, then the included header file might be protected by
`#ifdef _SYSEXITS_H' (in fact, it is, on GNU/Linux) which will prevent
its contents from being included.
Index: lib/sysexit_.h
