From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262811AbTDZRD6 (ORCPT ); Sat, 26 Apr 2003 13:03:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262849AbTDZRD6 (ORCPT ); Sat, 26 Apr 2003 13:03:58 -0400 Received: from [81.80.245.157] ([81.80.245.157]:61576 "EHLO smtp.alcove-fr") by vger.kernel.org with ESMTP id S262811AbTDZRDz (ORCPT ); Sat, 26 Apr 2003 13:03:55 -0400 Date: Sat, 26 Apr 2003 19:15:18 +0200 From: Stelian Pop To: Ben Collins Cc: Linux Kernel Mailing List Subject: Re: The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ] Message-ID: <20030426171518.GF18917@vitel.alcove-fr> Reply-To: Stelian Pop Mail-Followup-To: Stelian Pop , Ben Collins , Linux Kernel Mailing List References: <20030423144857.GN354@phunnypharm.org> <20030423152914.GM820@hottah.alcove-fr> <20030423202002.GA10567@vitel.alcove-fr> <20030423202453.GA354@phunnypharm.org> <20030423204258.GB10567@vitel.alcove-fr> <20030426082956.GB18917@vitel.alcove-fr> <20030426144017.GD2774@phunnypharm.org> <20030426162323.GD18917@vitel.alcove-fr> <20030426162503.GF2774@phunnypharm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030426162503.GF2774@phunnypharm.org> User-Agent: Mutt/1.3.25i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 26, 2003 at 12:25:04PM -0400, Ben Collins wrote: > Now if I couldn't reproduce the bug, I'd go back to you in a attempt to > test patches and pinpoint the problem. That just isn't the case here. > Once I reproduce the problem, your job is done. It is done from your point of view but not mine. You expect people to find bugs and report to you. I expect the bug to be fixed and the solution be given to me. See the difference ? Look I'm not a luser, I do maintain several projects myself, so it's not like I'm talking of osmething I don't fully understand. When someone reports a bug, even if I can fix and test the fix myself, I do have the respect to let the reported know it is fixed, and how and when he will get the fix. > > As I said in the previous mail, I did check the archives and saw nothing > > trivially relevant. But of course, I could have missed something. > > Then you must not be looking in the proper place. Thanks for pointing me to the right thread then. > But not all...I personally choose to keep specific discussions about > linux1394 on the linux1394 mailing lists. That's not to say I wont > respond on this list, but it is to say that if I announce something > important, it will be there and only there. If the final point is that you just *don't want'* sending an announce mail (either here or on your own linux1394-announce) than I think it is clear why we had all this thread. > > Sounds to me like you want to be in the middle of me and Marcelo. That > neither I nor him have the ability to agree on what patches should and > should not be moved from Linux1394 to the 2.4.x tree. Do you want either > or both of our jobs? I never said that, and you know it. But it is part of maintainer job to answer to criticism and be open to suggestions. I don't think there is anymore to get from this discussion, so let's end it there. Stelian. -- Stelian Pop Alcove - http://www.alcove.com