From: Andrew Cagney <ac131313@cygnus.com>
To: Mark Kettenis <kettenis@wins.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Get rid of redundant inclusion of <limits.h>
Date: Fri, 24 Aug 2001 09:06:00 -0000 [thread overview]
Message-ID: <3B867B90.3040506@cygnus.com> (raw)
In-Reply-To: <200108241221.f7OCLeE22049@delius.kettenis.local>
> Another step in reducing xm.h. We already include <limits.h> from
> "defs.h". No need to do it again from xm.h. Tested on
> sparc-sun-solaris2.6 (which includes config/xm-sysv4.h). Installed as
> an obvious fix (head only).
Just an aside, I'd not bother sitting on the other autoconf patches for
two weeks. I think they are ``in theory'' pretty obvious. We're only
going to find problem when they are committed.
Perhaphs instead, like Kevin was doing with K&R stuff, have a steady
trickle. If you're concerned about people being able to figure out
which change broke what then I'd just be careful to only commit one per
24 hours. That way `-D 2001-MM-DD-gmt'(1) can quickly be used to flip
between changes.
Keep it up!
Andrew
(1) The snapshots use this. They are always taken at exactly 00:00 UCT.
prev parent reply other threads:[~2001-08-24 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 5:21 Mark Kettenis
2001-08-24 9:06 ` Andrew Cagney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B867B90.3040506@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox