Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix prototype related breakage in go32-nat.c
Date: Sat, 11 Apr 2009 21:26:00 -0000	[thread overview]
Message-ID: <83skkeopab.fsf@gnu.org> (raw)
In-Reply-To: <200904112102.57302.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 11 Apr 2009 21:02:57 +0100
> 
> You know *now* that this happened before the dispute, but you didn't
> when you posted the patch and the question "Didn't we agree at the
> time that the prototypes should be corrected as well?" --- why did
> you need to ask it?

Because it seemed to me that the change which failed to update the
prototypes was the subject of that dispute.  But that was due to a
honest mistake, whereas the comment about ``needless forward
declarations'' was not.

> I can only assume that people interested in keeping the port alive
> will be the people that build it most frequently.  And I assumed
> that the port maintainer would build it regularly.

I'm doing my best.  I'm alone.  There's no one to come and help.  It's
not easy, what with my non-existent free time, of which I invest a
large portion into timely reviews of the GDB docs patches (which of
course has priority over taking care of the DJGPP build).

Back in August I thought that the DJGPP port had no users, because I
didn't hear from the DJGPP news group for a long time.  But it turned
out this was because of some snafu between my account on gnu.org and
DJ's server, which DJ fixed a couple of months ago, and since then
I've seen that the forum is alive and kicking, and people are
evidently still using DJGPP ports.  So I'm trying to revive GDB as
well, after I did the same with Emacs.

It's not easy, but I'm doing it.  All I'm asking for is a bit of
sympathy, and a small effort here and there.  Is that too much to ask
from a community to which I contribute every single week?


  reply	other threads:[~2009-04-11 21:26 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 [this message]
2009-04-13 16:51         ` Tom Tromey
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=83skkeopab.fsf@gnu.org \
    --to=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