From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa cvs & kernel sources
Date: Mon, 03 Mar 2003 17:34:14 +0100 [thread overview]
Message-ID: <s5hheakh0jd.wl@alsa2.suse.de> (raw)
In-Reply-To: <200303031620.h23GKxk10083@linuxaudiosystems.com>
At Mon, 3 Mar 2003 11:20:59 -0500,
Paul Davis wrote:
>
> jaroslav - how often do you sync with linus ? i am wondering what the
> best approach is for maintaining my ALSA source base given that i am
> now building and running 2.5. i'd prefer to use ALSA CVS ...
for getting the latest version with 2.5, you can copy the files in
alsa-kernel directories to the corresponding places of 2.5 kernel
tree, such as,
alsa-kernel/core -> linux-2.5.xx/sound/core
alsa-kernel/include -> linux-2.5.xx/include/sound
...
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-03-03 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 16:20 alsa cvs & kernel sources Paul Davis
2003-03-03 16:34 ` Takashi Iwai [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=s5hheakh0jd.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.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.