From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@lists.sourceforge.net
Subject: management of codes (linux 2.5 inclusion)
Date: Thu, 14 Feb 2002 17:15:00 +0100 [thread overview]
Message-ID: <s5hheok3urf.wl@alsa2.suse.de> (raw)
now a realistic question:
how do we manage the alsa driver codes together with linux 2.5 tree?
will be like before, i.e. occasionally Jaroslav sends patches to Linus
(or directly to bk) based on the alsa cvs?
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next reply other threads:[~2002-02-14 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 16:15 Takashi Iwai [this message]
2002-02-14 16:34 ` management of codes (linux 2.5 inclusion) Jaroslav Kysela
2002-02-14 23:11 ` Frank van de Pol
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=s5hheok3urf.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
/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.