mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dimitrie Paun <dimi@intelliware.ca>
To: "'Linus Torvalds'" <torvalds@transmeta.com>,
	Abramo Bagnara <abramo@alsa-project.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christoph Hellwig <hch@ns.caldera.de>,
	Jaroslav Kysela <perex@suse.cz>,
	sound-hackers@zabbo.net, linux-sound@vger.rutgers.edu,
	linux-kernel@vger.kernel.org
Subject: RE: [s-h] Re: ALSA patch for 2.5.2pre9 kernel
Date: Mon, 7 Jan 2002 14:03:26 -0500	[thread overview]
Message-ID: <F7EB06D3ED62D311A15600104B6D909F442058@IWD_MAIL> (raw)

> From: Linus Torvalds [mailto:torvalds@transmeta.com]
> 
> This is my current feeling.
> 
> However, la donna é mobile, and I'm a primus donna, fer 
> shure. So don't take it _too_ seriously, continue to argue 
> the merits of other approaches.

That's good to know. So let's do so:

There is no one grouping: things can be grouped in any number 
of ways, and for this very reason, a strictly hierarchical
grouping does not cut it. What I'm trying to say is that at
certain point, a given grouping characteristics becomes less 
important (say sound) and other (which crosscut other parts of
the source) increase in importance (say drivers).

For this reason, I think the current organization (net/core +
drivers/net) is more practical then the one which initially 
screams at any CompSci guy (net/core + net/drivers). 

Now, whichever one we choose, I'd _hate_ to see net organized
one way and sound the other way. It would be just ugly. That,
together with the fact that I don't think that putting everything
under sound/ is in any way superior to the current method,
I would suggest we stick to: sound/core + drivers/sound.

--
Dimi.

             reply	other threads:[~2002-01-07 19:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 19:03 Dimitrie Paun [this message]
     [not found] <20020108102833.A2927@werewolf.able.es>
2002-01-08  9:30 ` J.A. Magallon
2002-01-08  9:52   ` Abramo Bagnara
2002-01-08 10:12   ` Takashi Iwai
2002-01-08 10:18     ` Jaroslav Kysela
2002-01-08 10:36       ` Abramo Bagnara
2002-01-08 10:50         ` Jaroslav Kysela
2002-01-08 10:28     ` Abramo Bagnara
2002-01-08 10:41       ` Jaroslav Kysela
2002-01-08 10:34     ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07 23:44 J.A. Magallon
2002-01-08  2:01 ` [s-h] " Alan Cox
2002-01-08  5:12   ` Linus Torvalds
2002-01-07 20:51 Steven Walter
2002-01-07 18:10 Arnaldo Carvalho de Melo
2002-01-08  2:13 ` [s-h] " Alan Cox
2002-01-08 12:47   ` Arnaldo Carvalho de Melo
2002-01-07 18:00 Linus Torvalds
2002-01-07 18:19 ` [s-h] " Abramo Bagnara
2002-01-07 18:29   ` Linus Torvalds
2002-01-07 18:39     ` Abramo Bagnara
2002-01-07 18:47       ` Linus Torvalds
2002-01-07 19:09         ` Abramo Bagnara
2002-01-07 19:21         ` Pozsar Balazs
2002-01-07 20:29         ` Jauder Ho
2002-01-14  3:10         ` Pavel Machek
2002-01-07 21:25   ` Christoph Hellwig
2002-01-08  1:16     ` Timothy Covell
2002-01-08  2:53     ` Miles Lane

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=F7EB06D3ED62D311A15600104B6D909F442058@IWD_MAIL \
    --to=dimi@intelliware.ca \
    --cc=abramo@alsa-project.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@ns.caldera.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.rutgers.edu \
    --cc=perex@suse.cz \
    --cc=sound-hackers@zabbo.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®