From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ian Lance Taylor <ian@airs.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: [RFA] Eliminate warnings about snprintf declaration
Date: Sun, 15 May 2005 20:26:00 -0000 [thread overview]
Message-ID: <20050515195522.GA19088@nevyn.them.org> (raw)
In-Reply-To: <01c55986$Blat.v2.4$2a6b6c20@zahav.net.il>
On Sun, May 15, 2005 at 10:40:59PM +0300, Eli Zaretskii wrote:
> > Date: Sun, 15 May 2005 13:04:35 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Eli Zaretskii <eliz@gnu.org>, gcc-patches@gcc.gnu.org,
> > gdb-patches@sourceware.org, binutils@sourceware.org
> >
> > > > bfd/ChangeLog:
> > > > 2005-05-14 Eli Zaretskii <eliz@gnu.org>
> > > >
> > > > * configure.in: Add snprintf and vsnprintf to AC_CHECK_DECLS.
> > >
> > > These patches are approved, plus the change to libiberty/configure.ac
> > > which needs the obvious ChangeLog entry. Thanks.
> >
> > Eli, please mention regenerating configure in the ChangeLog.
>
> I didn't send patches for the (regenerated) configure and config.in.
> Should I do that, given that I cannot commit them anyway?
No, you don't need to. If you mention them in the ChangeLog, that'll
serve as a hint to whoever commits the patch which files need to be
regenerated.
> > Same comment as above applies; please mention configure.
>
> (And config.in, right?) Will do.
Good catch. Yes, thank you.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-15 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41994B9D.9080809@gnu.org>
[not found] ` <01c55702$Blat.v2.4$d4764900@zahav.net.il>
[not found] ` <20050512150804.GA1808@nevyn.them.org>
[not found] ` <01c55708$Blat.v2.4$cfc9f040@zahav.net.il>
[not found] ` <20050512154716.GA3513@nevyn.them.org>
[not found] ` <01c5570e$Blat.v2.4$1c533160@zahav.net.il>
[not found] ` <20050512162453.GA5180@nevyn.them.org>
[not found] ` <01c55732$Blat.v2.4$e9bd3640@zahav.net.il>
[not found] ` <20050512205103.GB13519@nevyn.them.org>
[not found] ` <01c5586c$Blat.v2.4$a7dfc720@zahav.net.il>
[not found] ` <20050514141204.GA10684@nevyn.them.org>
2005-05-14 19:02 ` Eli Zaretskii
2005-05-15 16:52 ` Ian Lance Taylor
2005-05-15 17:28 ` Daniel Jacobowitz
2005-05-15 19:48 ` Eli Zaretskii
2005-05-15 20:26 ` Daniel Jacobowitz [this message]
2005-05-20 12:55 ` Eli Zaretskii
2005-05-28 11:38 ` Eli Zaretskii
2005-05-28 12:43 ` Andreas Jaeger
2005-05-28 21:48 ` Eli Zaretskii
2005-05-30 17:50 ` DJ Delorie
2005-05-15 19:55 ` Eli Zaretskii
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=20050515195522.GA19088@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ian@airs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).