From: Jay Kasberger <JLKasberger@lbl.gov>
To: sourcenav@sources.redhat.com
Subject: You people rule.
Date: Mon, 04 Dec 2000 18:56:00 -0000 [thread overview]
Message-ID: <3A2C5A11.387AB842@lbl.gov> (raw)
Hi,
I just wanted to let you know - as I'm sure you already do - that
Source-Navigator is truly an excellent product. We use it here at
Lawrence Berkeley National Laboratory for genome project code, and we
couldn't be happier. It's very well thought out, powerful, and
extremely easy to use.
If you're interested, here's a feature suggestion: how about a way to
export all your different build configurations into a single Makefile,
with a build target for each configuration? Just an idea. Anyway, keep
up the good work, and best of luck in future endeavors.
next reply other threads:[~2000-12-04 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 18:56 Jay Kasberger [this message]
2000-12-04 19:49 ` Syd Polk
2000-12-04 20:04 ` Ben Elliston
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=3A2C5A11.387AB842@lbl.gov \
--to=jlkasberger@lbl.gov \
--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).