Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: dje@google.com, gdb@sourceware.org
Subject: Re: A new strategy for internals documentation
Date: Fri, 09 Aug 2013 09:35:00 -0000	[thread overview]
Message-ID: <83siyjrytv.fsf@gnu.org> (raw)
In-Reply-To: <520423A2.6010304@earthlink.net>

> Date: Thu, 08 Aug 2013 16:02:58 -0700
> From: Stan Shebs <stanshebs@earthlink.net>
> CC: Doug Evans <dje@google.com>, gdb@sourceware.org
> 
> I'm not sure what we're arguing at this point

I'm done arguing.  I regret I responded to your original message,
because all that did is cause me aggravation and open old wounds.
(Yes, it hurts to try to contribute to a community only to see the
attempts rejected time and again.)

> so let me see if I can summarize your views on specific actions:

Let me do it for you:

 . delete gdbint.texinfo (and the Makefile rules to go with it)

 . don't ever bother me again with any documentation of the GDB
   internals, because, following the 1st step above, I will resign
   from my responsibilities regarding (mis)documentation of the
   internals

 . you want to have a wiki or Doxygen comments or whatever, you don't
   need my approval anymore, see above; I was never asked to review
   code comments until now anyway

One last bit is that changing the format of a GNU manual might need to
be communicated to the FSF, I think.  Or maybe a majority vote by the
SC will be enough, I don't know (and don't care).

OK?


  parent reply	other threads:[~2013-08-09  9:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 22:26 Stan Shebs
2013-08-07  4:28 ` Eli Zaretskii
2013-08-07 19:58   ` Stan Shebs
2013-08-08 17:28     ` Eli Zaretskii
2013-08-08 21:08       ` Doug Evans
2013-08-08 21:56         ` Eli Zaretskii
2013-08-08 23:03           ` Stan Shebs
2013-08-09  8:08             ` John Gilmore
2013-08-09  9:53               ` Eli Zaretskii
2013-08-09  9:35             ` Eli Zaretskii [this message]
2013-08-09 23:04               ` Stan Shebs
2013-08-09  9:53             ` Mark Kettenis
2013-08-09 23:28               ` Stan Shebs
2013-08-08 23:04           ` Doug Evans
2013-08-09  9:13             ` Eli Zaretskii
2013-08-10  1:13             ` Yao Qi
2013-08-21 18:09     ` Steinar Bang
2013-08-21 20:02       ` Eli Zaretskii
2013-08-22 18:29         ` Steinar Bang
2013-08-08  3:45   ` Yao Qi
2013-08-08 17:31     ` Eli Zaretskii
2013-08-09  1:30       ` John Gilmore
2013-08-09  9:26         ` Eli Zaretskii
2013-08-09 18:16           ` Tom Tromey
2013-08-09 18:36             ` Eli Zaretskii
2013-08-09 22:31         ` Stan Shebs
2013-08-09 23:32           ` Matt Rice
2013-08-10  2:24           ` John Gilmore
2013-08-08 20:43   ` Tom Tromey
2013-08-08 20:57   ` Doug Evans
2013-08-08 20:41 ` Tom Tromey

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=83siyjrytv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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