From: jtc@redback.com (J.T. Conklin)
To: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH]: Missing changelog entries
Date: Tue, 06 Mar 2001 19:36:00 -0000 [thread overview]
Message-ID: <5mu2561c95.fsf@jtc.redback.com> (raw)
In-Reply-To: <5m1ysa2rzt.fsf@jtc.redback.com>
>>>>> "jtc" == J T Conklin <jtc@redback.com> writes:
jtc> Here are the ChangeLog entries for those changes that slipped in with
jtc> the last commit.
Ok, here they really are:
* Makefile.in (LINTFLAGS): Update to contain all of the macros
which define include paths used when compiling.
* util.c (savestring, msavestring): Change type of length argument.
* defs.h (savestring, msavestring): Update to match.
Bleh. I'm going home before I screw something else up. :-)
--jtc
--
J.T. Conklin
RedBack Networks
prev parent reply other threads:[~2001-03-06 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 19:11 J.T. Conklin
2001-03-06 19:36 ` J.T. Conklin [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=5mu2561c95.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=gdb-patches@sourceware.cygnus.com \
/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