From: Andrew Cagney <cagney@gnu.org>
To: Robert Millan <zeratul2@wanadoo.es>
Cc: gdb-patches@sources.redhat.com, glibc-bsd-hackers@nongnu.org
Subject: Re: [PATCH] GNU/k*BSD fixes (w/ChangeLog) [gdb]
Date: Tue, 27 Jan 2004 04:08:00 -0000 [thread overview]
Message-ID: <4015E442.9020304@gnu.org> (raw)
In-Reply-To: <20040111193933.GA2018@aragorn>
> Sanity check here? These changes to config.guess and config.sub are in
>> the upstream config sources? If they are I can just import new versions.
>
>
> Sure they are.
Good. I'll pull in a more up-to-date version shortly (its a standard
part of cutting a GDB branch).
> for gdb/ChangeLog:
>
> 2003-12-29 Robert Millan <robertmh@gnu.org>
>
> * configure.host: Match knetbsd*-gnu and kfreebsd*-gnu.
> * configure.tgt: Likewise.
>
I've committed this.
Andrew
next prev parent reply other threads:[~2004-01-27 4:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 23:14 Robert Millan
2004-01-11 19:27 ` Andrew Cagney
2004-01-11 19:45 ` Robert Millan
2004-01-24 19:24 ` Robert Millan
2004-01-27 4:08 ` Andrew Cagney [this message]
2004-01-27 19:22 ` Robert Millan
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=4015E442.9020304@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=glibc-bsd-hackers@nongnu.org \
--cc=zeratul2@wanadoo.es \
/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