From: Patrick Shirkey <pshirkey@boosthardware.com>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Re: bug tracking?
Date: Tue, 20 May 2003 22:25:08 +0900 [thread overview]
Message-ID: <3ECA2CB4.2030701@boosthardware.com> (raw)
In-Reply-To: 3ECA12B5.3050903@superbug.demon.co.uk
James Courtier-Dutton wrote:
> I would tend to disagree with you here. I think that it is vital that
> the person submitting the bug does log in, and has a verified email
> address.
This could be solved by not allowing the form to submit until they
provide an email address.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-20 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 6:07 [Fwd: Re: [Jackit-devel] OSS Backend] Patrick Shirkey
2003-05-15 8:58 ` Takashi Iwai
2003-05-15 9:21 ` bug tracking? Jaroslav Kysela
2003-05-15 9:37 ` Takashi Iwai
2003-05-15 10:12 ` Patrick Shirkey
2003-05-15 12:53 ` Takashi Iwai
2003-05-20 2:01 ` Patrick Shirkey
2003-05-20 11:34 ` James Courtier-Dutton
2003-05-20 13:25 ` Patrick Shirkey [this message]
2003-05-20 14:11 ` Takashi Iwai
2003-05-20 14:51 ` Erik Inge Bolsø
2003-05-20 16:16 ` Patrick Shirkey
2003-05-20 16:46 ` Paul Davis
2003-05-20 16:02 ` Patrick Shirkey
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=3ECA2CB4.2030701@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.