From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: script to check for guaranteed-to-crash-your-app warnings
Date: Wed, 07 Jan 2004 01:56:31 +0000 [thread overview]
Message-ID: <16379.26447.279073.661994@napali.hpl.hp.com> (raw)
In-Reply-To: <16379.11171.475075.708058@napali.hpl.hp.com>
Argh, the situation must be worse than what I reported, since
"evolution" didn't show up at all! evolution was missed because lynx
by default wraps lines after 80 columns. I fixed the fetch-log script
and am rerunning it now. I'm sure this would be a lot easier to do
for someone who has direct access to the log files...
--david
next prev parent reply other threads:[~2004-01-07 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 21:41 script to check for guaranteed-to-crash-your-app warnings David Mosberger
2004-01-06 21:46 ` Randolph Chung
2004-01-07 1:46 ` David Mosberger
2004-01-07 1:56 ` David Mosberger [this message]
2004-01-07 4:48 ` David Mosberger
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=16379.26447.279073.661994@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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