From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Ben Collins <bcollins@debian.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ]
Date: Sat, 26 Apr 2003 19:15:18 +0200 [thread overview]
Message-ID: <20030426171518.GF18917@vitel.alcove-fr> (raw)
In-Reply-To: <20030426162503.GF2774@phunnypharm.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 <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
next prev parent reply other threads:[~2003-04-26 17:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 12:29 IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Tony Spinillo
2003-04-23 12:53 ` Stelian Pop
2003-04-23 13:01 ` Ben Collins
2003-04-23 13:22 ` Stelian Pop
2003-04-23 13:32 ` Ben Collins
2003-04-23 13:46 ` Ben Collins
2003-04-23 13:58 ` Stelian Pop
2003-04-23 13:54 ` Ben Collins
2003-04-23 14:21 ` Stelian Pop
2003-04-23 14:23 ` Ben Collins
2003-04-23 14:51 ` Stelian Pop
2003-04-23 14:44 ` Ben Collins
2003-04-23 14:48 ` Ben Collins
2003-04-23 15:29 ` Stelian Pop
2003-04-23 19:13 ` Marcelo Tosatti
2003-04-23 19:05 ` Ben Collins
2003-04-23 19:27 ` Marcelo Tosatti
2003-04-23 20:20 ` Stelian Pop
2003-04-23 20:24 ` Ben Collins
2003-04-23 20:42 ` Stelian Pop
2003-04-26 8:29 ` The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ] Stelian Pop
2003-04-26 14:34 ` Ben Collins
2003-04-26 16:10 ` Stelian Pop
2003-04-26 16:12 ` Ben Collins
2003-04-26 17:00 ` Stelian Pop
2003-04-26 16:59 ` Ben Collins
2003-04-26 14:40 ` Ben Collins
2003-04-26 16:23 ` Stelian Pop
2003-04-26 16:25 ` Ben Collins
2003-04-26 17:15 ` Stelian Pop [this message]
2003-04-24 21:44 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Bill Davidsen
2003-04-24 21:41 ` Ben Collins
2003-04-25 18:06 ` Bill Davidsen
2003-04-25 18:16 ` Ben Collins
2003-04-26 10:36 ` Bill Davidsen
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=20030426171518.GF18917@vitel.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).