From: Ralph Jennings <ralph@oro.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] RE: emails
Date: Tue, 13 Mar 2001 13:16:21 -0800 [thread overview]
Message-ID: <20010313131621.A8580@d3.front> (raw)
In-Reply-To: <20010312172433.G31067@sistina.com>; from lewis@sistina.com on Mon, Mar 12, 2001 at 05:24:33PM -0600
On Mon, Mar 12, 2001 at 05:24:33PM -0600, AJ Lewis wrote:
> That might make sense. Can we assume everyone has access to a browser and
> will be willing to use if for bug reports? I know it makes it a lot easier
> for us as developers to track the bugs if they are reported there, but I'm
> not sure that everyone is willing to do so. Plus, many times people send
> bug reports from the console during the LVM install process, and so may not
> have easy access to a browser. I know Heinz initially had some concern about
> limiting file size on the list, so we'll have to get his opinion on this.
Somebody oughta write a program that figures exactly what
version of LVM, Kernel, and LVM tools are installed, and
writes the bug report for you. Debian has something like
this called "bug". You run "bug mutt", and it figures out
all the versions of mutt, the kernel (uname -a), and the
libraries that mutt depends on. You just give it the
program, a description of the bug, and the severity, and
it fills in the bug report and e-mails it for you. Very
nice when you find a bug, but you're in the middle of
something and don't have the time to research and figure
everything out yourself. It'll even attach the core file
if you want.
-Ralph
prev parent reply other threads:[~2001-03-13 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 21:53 [linux-lvm] RE: emails Jones, Steven
2001-03-12 22:15 ` AJ Lewis
2001-03-12 22:27 ` Eric M. Hopper
2001-03-12 23:02 ` Andreas Dilger
2001-03-12 23:24 ` AJ Lewis
2001-03-13 1:35 ` Heinz J. Mauelshagen
2001-03-13 21:16 ` Ralph Jennings [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=20010313131621.A8580@d3.front \
--to=ralph@oro.net \
--cc=linux-lvm@sistina.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 NNTP newsgroup(s).