public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sources.redhat.com
Subject: Helping new SN users (Re: Printing XREF from SN 5.0)
Date: Tue, 29 May 2001 16:31:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1010529162046.11247A-100000@cse.cygnus.com> (raw)
In-Reply-To: <3B14207A.190F9B82@tr.comm.mot.com>

On Tue, 29 May 2001, Hugo Varotto wrote:

> Hi Mo,

Hi Hugo.
 
> could you please expand a little bit what you need with respect to the README
> files ? I'm not an expert writing documentation neiter an expert in Source
> Navigator, but I'll try to help as much as I can.
> 
> Hugo

For one thing, we want to try to stick to existing best practices.

ftp://ftp.gnu.org/pub/gnu/standards/standards.text

I would think a README and INSTALL file at the very least.
There is already a toplevel README but it does not help
much. What we want it a README that tells people a bit
about Source-Navigator, what it does, why it is useful,
and where to find info about how to build and INSTALL it.

The goal of these initial help files is simply to help
people get started. We don't want people to give up
without even trying simply because they don't know
where to get started (sadly, this is a real problem).

Of course, if you want to know what types of getting
started questions folks are likely to ask, just
go to the source.

http://sources.redhat.com/ml/sourcenav/

Mo DeJong
Red Hat Inc

      reply	other threads:[~2001-05-29 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23  4:19 printout Eckhard Fröbel
2001-05-24  8:13 ` Printing XREF from SN 5.0 Hugo Varotto
2001-05-24 12:15   ` Mo DeJong
2001-05-24 12:37     ` Mo DeJong
2001-05-24 13:40       ` Hugo Varotto
2001-05-24 13:49         ` Mo DeJong
2001-05-29 15:19           ` Hugo Varotto
2001-05-29 16:31             ` Mo DeJong [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=Pine.SOL.3.91.1010529162046.11247A-100000@cse.cygnus.com \
    --to=mdejong@cygnus.com \
    --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).