From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MI non-stop 0/11] Series overview
Date: Sat, 28 Jun 2008 18:20:00 -0000 [thread overview]
Message-ID: <uabh5ctt4.fsf@gnu.org> (raw)
In-Reply-To: <g45se6$569$1@ger.gmane.org>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 28 Jun 2008 21:29:44 +0400
>
> > What about documenting the new features?
>
> Why do you think the MI non-stop spec and the thread behaviour spec were written?
> As usual, and even more than usual due to huge amount of text, I'm not going to
> mess with texinfo until I'm sure nobody has big objections about the behaviour.
I just didn't see anything about the docs, not even a note saying it
will be posted later. Nothing to get angry about.
Btw, you don't need to mess with Texinfo if you don't want to. You
can write the documentation as free text, and I will add Texinfo
markup.
next prev parent reply other threads:[~2008-06-28 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 16:38 Vladimir Prus
2008-06-28 17:33 ` Eli Zaretskii
2008-06-28 17:35 ` Vladimir Prus
2008-06-28 18:11 ` Stan Shebs
2008-06-29 5:38 ` Vladimir Prus
2008-06-28 18:20 ` Eli Zaretskii [this message]
2008-06-29 5:47 ` Vladimir Prus
2008-06-29 17:49 ` 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=uabh5ctt4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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