From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Command trace testsuite
Date: Thu, 10 Aug 2006 20:30:00 -0000 [thread overview]
Message-ID: <uzmece6yt.fsf@gnu.org> (raw)
In-Reply-To: <44DB5BE4.6070704@st.com> (message from Andrew STUBBS on Thu, 10 Aug 2006 17:16:36 +0100)
> Date: Thu, 10 Aug 2006 17:16:36 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
>
> How about the attached for the NEWS file?
Okay, but...
> + Print each CLI command as it is executed. Each command is prefixed with
> + a number of `+' symbols representing the nest depth.
^^^^
I think ``nesting'' is better here.
next prev parent reply other threads:[~2006-08-10 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 17:05 Andrew STUBBS
2006-08-08 17:34 ` Daniel Jacobowitz
2006-08-10 16:16 ` Andrew STUBBS
2006-08-10 17:12 ` Daniel Jacobowitz
2006-08-10 19:13 ` Andrew STUBBS
2006-08-10 20:30 ` Eli Zaretskii [this message]
2006-08-14 7:32 ` Andrew STUBBS
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=uzmece6yt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sourceware.org \
/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