From: "Alfred M. Szmidt" <ams@kemisten.nu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: [PATCH] Fix GNU/Hurd build error
Date: Sat, 14 Jun 2003 17:18:00 -0000 [thread overview]
Message-ID: <E19REes-0004Wh-00@lgh163a.kemisten.nu> (raw)
In-Reply-To: <20030614161900.GA6388@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 14 Jun 2003 12:19:00 -0400)
No, judging from the response apparently no one in the GDB world
cares about GNU. GDB's response time to patches is slow; live with
it instead of placing demands upon volunteers.
Placing demands on volunteers is reasonable if there is a patch out,
and if the patch looks OK, since commiting something takes no time at
all. But thats just my opinion.
The patch looks reasonable, so I have checked it in.
Thanks.
next prev parent reply other threads:[~2003-06-14 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030529131545.GA458@pc-jeroen>
2003-06-14 16:01 ` Alfred M. Szmidt
2003-06-14 16:19 ` Daniel Jacobowitz
2003-06-14 16:30 ` Andrew Cagney
2003-06-14 17:18 ` Alfred M. Szmidt [this message]
2003-06-14 17:36 ` Andrew Cagney
2003-06-14 20:07 ` Alfred M. Szmidt
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=E19REes-0004Wh-00@lgh163a.kemisten.nu \
--to=ams@kemisten.nu \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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).