From owner-freebsd-multimedia Wed Jul 29 21:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26341 for freebsd-multimedia-outgoing; Wed, 29 Jul 1998 21:31:50 -0700 (PDT) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26332; Wed, 29 Jul 1998 21:31:41 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA03753; Wed, 29 Jul 1998 21:31:24 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807300431.VAA03753@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: marc@bowtie.nl, Nate Williams , Flemming Jacobsen , dburr@pobox.com (Donald Burr), freebsd-multimedia@FreeBSD.ORG, phk@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: The future of the bt848 driver? (FW: cvs commit: CVSROOT avail) In-reply-to: Your message of "Wed, 29 Jul 1998 11:59:57 PDT." <14761.901738797@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 21:31:24 -0700 From: Amancio Hasty Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On one hand I can conceive that it is neccessary at times to use the > > "I'm a core member argument", on the other hand, this should be a last > > resort, if all other methods fail to reach an agreement. > > That's not really what happened in this case, nor could it obviously > have happened in John's case (insert sideways look at "scrappy" here) > since John was also a core member at the time. Sometimes people just Excuse me, allow me to refresh your memory 8) ------------------------------------------------------------------------------ Date: Wed, 15 Jul 1998 00:56:18 -0700 From: Amancio Hasty To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci brooktree848.c Message-ID: <199807150756.AAA00917@rah.star-gate.com> In response to: sos@FreeBSD.ORG said: > sos 1998/07/14 14:20:00 PDT > Modified files: > sys/pci brooktree848.c > Log: > Add support for the AVer Media range of cards. > Revision Changes Path > 1.45 +13 -9 src/sys/pci/brooktree848.c > In message <199807150359.UAA02946@rah.star-gate.com>, Amancio Hasty writes: > >Cute, I will review the patch later on the week after my work crunch. > > > >If the patch is not good it will be wipe out on my next rev level. > > WARNING: > > Do not wipe out other peoples patches, unless you provide > the same level of functionality in "your next rev level". Background, we in the multimedia list are in the process of improving the tuner detection code due mostly to the ever increasing proliferation of bt848/tuners . So far we have identified a popular bt848 vendor Hauppauge who stores its configuration information in an eeprom over the couple of weeks we engaged in decoding the eeprom and so far we have been successful. This was an important step for detecting the known good configurations helps reduce the search space for bt848/tuners. Prior to that I send out a general query to attempt to identify the basic characteristics of the cards and I am compiling a small database of bt848 / tuner cards -- in the mean time any code dealing with tuner detection addition/deletion has been frozen by me till I get a better handle on the proper identification of the bt848/tuner cards. I have a basic question, can any committer or so called "core" tramp over any code in the tree specially if they are not the author/mantainer of the code? PHK's e-mail seems to imply that is the case. Amancio ----------------------------------------------------------------------- I naturally received 0 responses to my posting to the hacker's mailing list nor any core member bother to ask for any clarification. As far as I am concerned it was business as usual after my plea to the hacker's mailing list and I was not included in any core correspondence dealing with this matter. My interpretation is that any core member can claim his right to just quite simply splash code over any third party's maintained code in the source tree and by virtue of being a core member makes the code intrusion a rightful act;furthermore , if you happen to disagree with the core member's act and wish to reverse the code intrusion you stand to have any core member remove your commit privileges. JKH, if this is not clear to you feel free to call me: 415-495-3046 Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message