On Thu, 9 Aug 2007 02:02:19 +0200 Michael Buesch <mb@xxxxxxxxx> wrote: > > I'm hopelessly confused by the ssb stuff. I'm not sure if I have all the > > right stuff, all the latest stuff and I don't understand why some is going > > into git-wireless and some is not. > > Everything is going into git-wireless. > git-wireless contains latest ssb. _but_ John complained > about that. And he is right. SSB is not strictly wireless core. > So I thought it was best to get ssb into mainline as soon as > possible. So -mm is really the way to go into mainline. > My plan was to merge mainline with the next merge window. > > > I'd prefer to be dumbly pulling a tree which Michael controls rather than > > trying to master it all in -mm, if possible. A git tree or a quilt tree in > > some open dir somewhere would suit? > > It's a bit difficult, as bcm43xx depends on it. Which again depends > on the wireless tree. :) > So basically we are stuck with maintaining it in wireless-dev. > > I don't know what your policy is with pulling from wireless-dev. > So wireless-dev currently contains latest SSB. So if you pull from > wireless-dev, you'll also get latest SSB. Though, if we want to > merge SSB soon, we need it broken-out. That is what I was trying > to do. Still confused. I pull git+ssh://master.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git#mm-master into -mm. Could be that John puts other things into other trees which do not appear in #mm-master, I don't know. Given that you are the developer and maintainer of ssb it is appropriate (especially at this stage) that you run a tree. Just a plain old quilt tree like http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/ would be fine. If that tree is relative to some tree which John is running then that's OK, as long as someone tells me where to get that tree from. Or just merge all of SSB via John's tree. I don't think it matters that it's not strictly a wireless thing. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
