From: Vladimir Prus <vladimir@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: Ping: frozen variable objects
Date: Wed, 18 Apr 2007 05:38:00 -0000 [thread overview]
Message-ID: <200704180938.17763.vladimir@codesourcery.com> (raw)
In-Reply-To: <ud525jsvh.fsf@gnu.org>
On Monday 16 April 2007 00:16, Eli Zaretskii wrote:
> > From: Nick Roberts <nickrob@snap.net.nz>
> > Date: Sun, 15 Apr 2007 23:54:49 +1200
> > Cc: Eli Zaretskii <eliz@gnu.org>, drow@false.org,
> > gdb-patches@sources.redhat.com
> >
> > > Here's an editorial patch based on comments from you, Dan and Nick. OK?
> >
> > It's Eli who decides, but having -var-update reference -var-set-frozen which in
> > turn references -var-update seems too complicated, and shouldn't be necessary
> > if there was a natural flow.
>
> I'm afraid I wasn't following this sub-thread closely enough, so
> forgive me, Vladimir, if I ask what was already said: could you please
> explain the rationale for your change of the anchors in this patch?
You've asked to add a reference to -var-update. There was already -var-update
anchor. However, that anchor was pointing in the middle of -var-update documentaiton,
so following the reference would land the reader at list of some attributes, which
would be confusing. And it seems that calling anchor for entire -var-update docs
as -var-update is more reasonable then using -var-update anchor for the list
of fields output by -var-update.
Does this clarify things?
- Volodya
next prev parent reply other threads:[~2007-04-18 5:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 9:52 Vladimir Prus
2007-03-25 20:17 ` Eli Zaretskii
2007-04-10 19:03 ` Daniel Jacobowitz
2007-04-11 14:44 ` Vladimir Prus
2007-04-11 14:52 ` Daniel Jacobowitz
2007-04-11 18:38 ` Eli Zaretskii
2007-04-13 9:53 ` Eli Zaretskii
2007-04-14 16:14 ` Vladimir Prus
2007-04-14 16:19 ` Daniel Jacobowitz
2007-04-14 23:18 ` Nick Roberts
2007-04-15 10:32 ` Vladimir Prus
2007-04-15 10:35 ` Vladimir Prus
2007-04-15 11:46 ` Nick Roberts
2007-04-15 11:57 ` Vladimir Prus
2007-04-15 20:09 ` Nick Roberts
2007-04-15 20:16 ` Eli Zaretskii
2007-04-15 20:13 ` Eli Zaretskii
2007-04-14 20:32 ` Eli Zaretskii
2007-04-15 11:42 ` Vladimir Prus
2007-04-15 12:03 ` Nick Roberts
2007-04-16 2:40 ` Eli Zaretskii
2007-04-18 5:38 ` Vladimir Prus [this message]
2007-04-18 10:37 ` Nick Roberts
2007-04-18 22:23 ` Eli Zaretskii
2007-04-19 4:41 ` Eli Zaretskii
2007-04-15 20:14 ` Eli Zaretskii
2007-04-15 8:04 ` Nick Roberts
2007-04-18 10:22 ` [patch] fix insight (was: Re: Ping: frozen variable objects) Brian Dessent
2007-04-18 12:51 ` Maciej W. Rozycki
2007-04-18 13:01 ` Brian Dessent
2007-04-18 5:38 ` Ping: frozen variable objects Michael Snyder
2007-04-18 6:57 ` Vladimir Prus
2007-04-18 22:21 ` Michael Snyder
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=200704180938.17763.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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