public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@redhat.com>
To: "Gilles J. Seguin" <segg@infonet.ca>, sourcenav@sources.redhat.com
Subject: Re: Future Development features (was: Asm files in SN)
Date: Mon, 24 Jul 2000 12:48:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20000724124935.00c60100@pop.cygnus.com> (raw)
In-Reply-To: <397BC70C.B892AE73@infonet.ca>

At 12:33 AM 7/24/00 -0400, Gilles J. Seguin wrote:
>Ben Elliston wrote:
> >
> > Note that the assembly language parser is specifically for PowerPC assembly
> > language.  It may not manage to detect anything useful in assembly 
> files for
> > other targets.  It's possible to generate your own, if you really want to.
> >
> > What kind of asm files are you trying to parse?
>
>I would appreciate if we can propose a whish list and future
>development features list, with desirable/important/urgent comments.
>
>What is S-N, what features we do not want.
>What we do not want Source-Navigator to become.
>
>Gilles J. Seguin

I would be happy to collect issues and centralize them into a web page, and 
put an ascii version of it in snavigator/TODO.


Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.



  reply	other threads:[~2000-07-24 12:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <964343111.31392.ezmlm@sources.redhat.com>
2000-07-23  2:23 ` Asm files in SN leonp
2000-07-23 15:58   ` Ben Elliston
2000-07-23 21:32     ` Future Development features (was: Asm files in SN) Gilles J. Seguin
2000-07-24 12:48       ` Syd Polk [this message]
2000-07-24  1:16     ` Asm files in SN leonp

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=4.2.0.58.20000724124935.00c60100@pop.cygnus.com \
    --to=spolk@redhat.com \
    --cc=segg@infonet.ca \
    --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).