public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: gimli <gimli@dark-green.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] S2API drivers sync
Date: Sat, 20 Dec 2008 10:54:47 +0100	[thread overview]
Message-ID: <494CC0E7.50505@dark-green.com> (raw)
In-Reply-To: <200812191943.00696.sinter.mann@gmx.de>

I think you do net get me right. I'm not blaming one person.
I blame the whohle DVB-S2 thing and the developers involved in.
You immedialey shoot, start thinking. It's not the fault of one
person. The mess is the fault of a group of persons. The only
thing i see on this ML is when criticism come up some people here
can't deal with it. That shows me verry little skills in dealing
with criticism and dealing with users and developers. Try to find
a solution and not blaming this or that person. One intresting point
on this ML is, that flames starting realy fast and are mostly
personal and more than rude. And most of the time there is no
technical solution discussion, only flaming and shooting.

cu

Edgar (gimli) Hucek

sinter schrieb:
> Am Freitag 19 Dezember 2008 18:01:40 schrieb gimli:
>> The DVB-S2 stuff smells all like a big bullshit.
>> In the first step a big hurry to get S2API in
>> the mainline kernel and now nothing at all from
>> the DVB-S2 front. This is a completly big mess
>> in my eyes.
>>
>> cu
>>
>> Edgar (gimli) Hucek
>>
>> P.S.: Childish political games which are played on
>> the shoulders of the users. Hurray, well done.
> 
> Yes, Edgar, exactly: This is what the name Manu A. stands for since this guy 
> was recruited as a DVB "maintainer" by Johannes Stezenbach:
> 
> Kiddish political games which are played on the shoulders of the users.
> Also those kiddish games are ideal to hide the discovery of one's own personal 
> mediocrity / incapability in coding issues.
> 
> There are people who ask themselves why Manu A. still owes a repository at 
> linuxtv.org. I guess this runs under "utilitarianism of human beings".
> 
> And also: a huge mass of (inactive) nominal members looks nice for a career at 
> redhat.com, doesn't it?
> 
> 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  parent reply	other threads:[~2008-12-20  9:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 18:04 [linux-dvb] S2API drivers sync gimli
2008-12-19 16:52 ` Oleg Roitburd
2008-12-19 17:01   ` gimli
2008-12-19 17:42     ` VDR User
2008-12-19 18:43     ` sinter
2008-12-19 19:29       ` Markus Rechberger
2008-12-19 19:58         ` sinter
2008-12-19 20:11           ` Markus Rechberger
2008-12-19 20:31             ` Michael Krufky
2008-12-19 20:47               ` Devin Heitmueller
2008-12-19 21:08                 ` Nicolas Will
2008-12-19 22:07                   ` [linux-dvb] Adding info to the wiki, Was: " Jos Hoekstra
2008-12-19 22:25                     ` Antti Palosaari
2008-12-19 22:39                     ` Nicolas Will
2008-12-19 22:31                   ` [linux-dvb] " Devin Heitmueller
2008-12-19 21:08               ` sinter
2008-12-19 23:53             ` Christophe Thommeret
2008-12-19 21:03           ` user.vdr
2008-12-20  9:54       ` gimli [this message]
2008-12-29 10:52         ` Jelle De Loecker

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=494CC0E7.50505@dark-green.com \
    --to=gimli@dark-green.com \
    --cc=linux-dvb@linuxtv.org \
    /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