2009/6/4 Ted Unangst <ted.unan...@gmail.com> > 2009/6/3 Christiano Farina Haesbaert <christiano...@gmail.com>: > > "Port driver y from xbsd" : "We need support for cards blablablabla" > > I think this right here demonstrates how far away you are from where > you need to be. If you don't have such hardware, your efforts at > supporting it are likely to be crap. If you do have the hardware, you > should already know whether it works or not.
Maybe a I gave a lame example. > > > You believe that the openbsd developers have insider knowledge that > makes them better at openbsd development? Then take it from one of > those developers: Lists of things to do are the wrong way to improve > openbsd. If you think you know better than we do, you don't the list. No, I believe they do know better than me what needs to be done, and by having a channel for us (newcomers) with these things would simply speed things up, if this is the way it is, as you say, ok, we'll help without the "list", take what Henning wrote in the previous email, I will start working on it this weekend and I firmly believe I will know what to do next. Again, if that's the way it is, that's the way we will help, but I truly fail to see how this isn't a win win situation. > > If you need the list, then you'll have to accept that the kind of > list you envision is a bad idea. That's just the way things are. > > It's not about where you start. It's about starting anywhere. Here, > watch, it's this easy: > find /usr/src -name "*.c" | random 10000
