From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dan Mann <mainlylinux@attbi.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
ALSA development <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: ALSA patch for 2.5.4
Date: Mon, 11 Feb 2002 19:23:02 -0500 [thread overview]
Message-ID: <3C686066.91B06D84@mandrakesoft.com> (raw)
In-Reply-To: 1013472766.19794.6.camel@localhost.localdomain
Dan Mann wrote:
> On Mon, 2002-02-11 at 09:16, Jaroslav Kysela wrote:
> > I repeat myself but anyway. We are open to any suggestions and
> > ideas for this kernel integration patch. Unfortunately, Linus has not
> > approved this directory tree and he is not talking with us at the time.
> > It seems that BIO changes are over, but he's probably busy enough to
> > ignore our e-mails with co-operation requests.
> There are at least 2 reasons that I can see why Linus probably won't
> accept your patch:
>
> 1. It is not an inline text attachment (it is a URL).
> 2. It is 79,000 lines long
Well, merging ALSA is going to be one big mother of a patch no matter
how you slice it :)
But I agree, it would be nice for the patch to be broken up into steps,
ie. first patch moves OSS drivers into new location, second patch adds
infrastructure, third patch adds the 1001 drivers that ALSA supports :)
Also if the ALSA guys wanted to experiment with BK, that would be a
great way to do the merge.
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dan Mann <mainlylinux@attbi.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
ALSA development <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: ALSA patch for 2.5.4
Date: Mon, 11 Feb 2002 19:23:02 -0500 [thread overview]
Message-ID: <3C686066.91B06D84@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0202111429270.500-100000@pnote.perex-int.cz> <1013472766.19794.6.camel@localhost.localdomain>
Dan Mann wrote:
> On Mon, 2002-02-11 at 09:16, Jaroslav Kysela wrote:
> > I repeat myself but anyway. We are open to any suggestions and
> > ideas for this kernel integration patch. Unfortunately, Linus has not
> > approved this directory tree and he is not talking with us at the time.
> > It seems that BIO changes are over, but he's probably busy enough to
> > ignore our e-mails with co-operation requests.
> There are at least 2 reasons that I can see why Linus probably won't
> accept your patch:
>
> 1. It is not an inline text attachment (it is a URL).
> 2. It is 79,000 lines long
Well, merging ALSA is going to be one big mother of a patch no matter
how you slice it :)
But I agree, it would be nice for the patch to be broken up into steps,
ie. first patch moves OSS drivers into new location, second patch adds
infrastructure, third patch adds the 1001 drivers that ALSA supports :)
Also if the ALSA guys wanted to experiment with BK, that would be a
great way to do the merge.
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-02-12 0:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 14:16 ALSA patch for 2.5.4 Jaroslav Kysela
2002-02-11 14:16 ` Jaroslav Kysela
2002-02-12 0:14 ` Dan Mann
2002-02-12 0:14 ` Dan Mann
2002-02-12 0:23 ` Jeff Garzik [this message]
2002-02-12 0:23 ` Jeff Garzik
2002-02-12 1:03 ` James Courtier-Dutton
2002-02-12 1:03 ` [Alsa-devel] " James Courtier-Dutton
2002-02-12 1:16 ` Alan Cox
2002-02-12 1:16 ` [Alsa-devel] " Alan Cox
2002-02-12 0:38 ` Linus Torvalds
2002-02-12 0:38 ` Linus Torvalds
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=3C686066.91B06D84@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mainlylinux@attbi.com \
--cc=perex@perex.cz \
--cc=torvalds@transmeta.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.