From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [commit] Fix prototype related breakage in go32-nat.c
Date: Mon, 13 Apr 2009 16:51:00 -0000 [thread overview]
Message-ID: <m3ab6ko5y0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83skkeopab.fsf@gnu.org> (Eli Zaretskii's message of "Sun\, 12 Apr 2009 00\:26\:20 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> It's not easy, but I'm doing it. All I'm asking for is a bit of
Eli> sympathy, and a small effort here and there. Is that too much to ask
Eli> from a community to which I contribute every single week?
No, it is not too much to ask. However, respect is a two-way street.
This patch could easily have gone in without finger-pointing. I'm
sure whoever neglected to update the prototypes did not do it on
purpose.
Tom
next prev parent reply other threads:[~2009-04-13 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 18:00 Eli Zaretskii
2009-04-11 18:15 ` Pedro Alves
2009-04-11 19:27 ` Eli Zaretskii
2009-04-11 20:02 ` Pedro Alves
2009-04-11 21:26 ` Eli Zaretskii
2009-04-13 16:51 ` Tom Tromey [this message]
2009-04-13 18:38 ` Eli Zaretskii
2009-04-11 21:41 ` 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=m3ab6ko5y0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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