Hey guys, stop beating dead horses and finding scapegoats. Whatever excuses you're going to find post-fact isn't going to change the fact that HE now has working code with functionality better than the broken crap currently in linux-dvb, and YOU don't. Users (what little of them Linux still has) usually want stuff that WORKS, and they don't give two shits about HOW it works underneath. So when you stop accepting working solutions because of some bullshit political/etc reason, everyone loses. Remember, each time someone creates a new distribution of Linux "to scratch an itch" because their changes were "too big" for some other specialized niche distro, the terrorists win. -tc On 6/30/07, Johannes Stezenbach <js@xxxxxxxxxxx> wrote: > On Thu, Jun 28, 2007, Markus Rechberger wrote: > > On 6/28/07, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> wrote: > > > > > > In general, it is a good idea to have the manufacturer supporting their > > > drivers. However, it won't make any sense to allow Empiatech to touch on > > > low-level drivers for hardware not developed by them. The original > > > patches were touching on every DVB driver, even on some Empiatech > > > competitors drivers. > > > > And it added support for several cx88 and saa7134 based devices. The > > base change was required to get the Empia drivers in, the rest was > > optional. > > There was a patch from another company which added full xc3028 support > > for their saa7134 drivers to the repository on mcentral.de and by > > doing what you did you now force me to rework what that company did. > > The whole issue is a bigger than you imagine. > > I wondered about the reasons for your reply in > http://marc.info/?l=linux-dvb&m=117940327206449&w=2 > > This now outlines what the problem is: You had a repository > which contained code which you knew wasn't going to be merged > because others disagreed, and instead of addressing the problem > you decided to work in isolation for a year, piling patch upon patch. > > But the original problem is still unsolved, and instead of asking > for help you try to force us to accept your code -- which > naturally won't work. > > Knowing how difficult the situation was I tried to resolve it > by suggesting to merge your code as-is, and then fix it up later > until everyone's happy with the outcome. > http://marc.info/?l=linux-video&m=117572695505842 ff. > > Everybody grudgingly agreed, and I thought the issue > was resolved, and I even sent you in private mail a reminder > to push your code in time to make the 2.6.22-rc1 merge window. > I was surprised that you never did. > > A few weeks later you start all over again with the same > "merge all my code" request, but this time I was thinking > that the reason why you didn't push your patches earlier > was that you don't want us to change anything to your code > after it has been merged. Which you confirmed in > http://marc.info/?l=linux-dvb&m=117940327206449&w=2 > > But your hybrid tuner dvb-core changes are too ugly to live, > if we can't fix them up then your code can't be merged. > > A few people have offered to help you, but it seems you > are unable to accept any help and rather pull the plug > than to allow others to change your code. > > I have the impression that you didn't get the basic idea > of what open source development is all about :-( > > > > Johannes > > _______________________________________________ > linux-dvb mailing list > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
