public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Lonnie L VanZandt" <tsys@uswest.net>
To: <sourcenav@sources.redhat.com>
Subject: xref and referred by?
Date: Tue, 17 Oct 2000 08:36:00 -0000	[thread overview]
Message-ID: <FAEGKJHOHCILEABGDOJJAECPCHAA.tsys@uswest.net> (raw)

Why is it that many times the Referenced By information is unavailable? More
often than not, I want to see who calls a function and not what that
function calls. However, I can't seem to get SN to display the Referenced By
information.

Do you have a FAQ I should have read before bothering you?

Thanks,
Lonnie.

             reply	other threads:[~2000-10-17  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-17  8:36 Lonnie L VanZandt [this message]
2000-10-17  8:45 ` Bruce Stephens
2000-10-18  1:11 dave.banham
2000-10-19  3:01 dave.banham
2000-10-19  7:58 ` Berek
2000-10-19 22:08 ` Mo DeJong
2000-11-14  8:55 Mark Thornber
2000-11-15  4:57 dave.banham

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=FAEGKJHOHCILEABGDOJJAECPCHAA.tsys@uswest.net \
    --to=tsys@uswest.net \
    --cc=sourcenav@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).