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: Sun, 29 Jun 2008 17:49:00 -0000 [thread overview]
Message-ID: <u1w2gcfcf.fsf@gnu.org> (raw)
In-Reply-To: <200806290937.18990.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sun, 29 Jun 2008 09:37:18 +0400
> Cc: gdb-patches@sources.redhat.com
>
> > 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.
>
> Does that mean I have to send a patch adding just a bunch of free text,
> or you prefer some other approach?
If you send plain text, a patch will not be useful, since I cannot
apply it, obviously. So just send the text itself, and tell in what
place in the manual you suggest to put it.
prev parent reply other threads:[~2008-06-29 17:37 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
2008-06-29 5:47 ` Vladimir Prus
2008-06-29 17:49 ` Eli Zaretskii [this message]
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=u1w2gcfcf.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