![]() | |||||||||||||
Messages in this thread |
Well, that's kinda silly to have two different approaches. If the consensus is to keep net/ and drivers/net/, why not just have sound/ and drivers/sound/ too? It is not a big stretch to grab sound/ and drivers/sound/ over just sound/ and certainly the proposal of having a subsys/ directory is essentially a rename of drivers/ to subsys/. so.... net/ sound/ drivers/net/ drivers/sound/ The drivers subdir structure closely follows what happens one level up. Not a problem and maintains the status quo. QED. --Jauder On Mon, 7 Jan 2002, Linus Torvalds wrote: > > On Mon, 7 Jan 2002, Abramo Bagnara wrote: > > > > Just to resume, you think that the way to go is: > > > > 1) to have sound/ with *all* sound related stuff inside > > 2) to leave drivers/net/ and net/ like they are now (because although > > it's suboptimal, to change it is a mess we don't want to face now) > > 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. > > Linus > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:15 [from the cache] ©2003-2008 | |||||||||||||