From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: keiths@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA 5/5] Explicit linespecs - documentation
Date: Wed, 01 Aug 2012 14:48:00 -0000 [thread overview]
Message-ID: <838vdyekk1.fsf@gnu.org> (raw)
In-Reply-To: <50190306.7080500@redhat.com>
> Date: Wed, 01 Aug 2012 11:20:54 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
>
> On 07/27/2012 12:23 PM, Eli Zaretskii wrote:
> > This is too implementation oriented, and thus not really appropriate
> > for the user manual. The text should:
> >
> > . explain what is an explicit spec, in a way that clarifies why it
> > is called "explicit" (so that users could make a mental note of
> > that, which will facilitate remembering the terminology);
>
> Or maybe (shocking suggestion follows), not even calling
> "explicit linespecs" "linespecs" at all. IOW, you either use linespecs,
> or explicit locations.
Not shocking at all, at least not for me. I could go with "explicit
locations". We still need to say at least something to explain what's
the "explicit" part doing there.
prev parent reply other threads:[~2012-08-01 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 3:50 Keith Seitz
2012-07-27 11:23 ` Eli Zaretskii
2012-08-01 10:21 ` Pedro Alves
2012-08-01 14:48 ` 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=838vdyekk1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=palves@redhat.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