All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conrad Parker <conrad@vergenet.net>
To: Erik de Castro Lopo <erikd-alsa@mega-nerd.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Removal of /proc/asound ?
Date: Tue, 20 May 2003 14:40:30 +1000	[thread overview]
Message-ID: <20030520044030.GD24175@vergenet.net> (raw)
In-Reply-To: <20030519200301.1c3276f7.erikd-alsa@mega-nerd.com>

On Mon, May 19, 2003 at 08:03:01PM +1000, Erik de Castro Lopo wrote:
> 
> I therefore strongly urge you to keep 2.4 functionality as it was and feel
> free to do whatever is needed for the 2.5/2.6 kernel.

erik, you're hassling the wrong people -- a script exists to make the
devices you want, this is a packaging problem for el Debian ALSA Psychos
(knowing that erik uses debian), and a bog-standard GOTCHA for CVS users,
unless it can be done by make install or something.

-- 
    <K
       <K
 <K


-------------------------------------------------------
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

  parent reply	other threads:[~2003-05-20  4:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 22:16 Removal of /proc/asound ? Erik de Castro Lopo
2003-05-17 11:55 ` Jaroslav Kysela
2003-05-17 22:13   ` Erik de Castro Lopo
2003-05-19  9:46     ` Takashi Iwai
2003-05-19 10:03       ` Erik de Castro Lopo
2003-05-19 10:21         ` Jaroslav Kysela
2003-05-20  4:40         ` Conrad Parker [this message]
2003-05-20  5:09           ` David B Harris
2003-05-20  5:48             ` Conrad Parker
2003-05-20  8:15               ` Erik de Castro Lopo
2003-05-20 11:37             ` James Courtier-Dutton
2003-05-19 16:36       ` Patrick Shirkey
2003-05-21 11:18         ` Takashi Iwai

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=20030520044030.GD24175@vergenet.net \
    --to=conrad@vergenet.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=erikd-alsa@mega-nerd.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 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.