From: Ben Collins <bcollins@debian.org>
To: Stelian Pop <stelian.pop@fr.alcove.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
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 10:40:18 -0400 [thread overview]
Message-ID: <20030426144017.GD2774@phunnypharm.org> (raw)
In-Reply-To: <20030426082956.GB18917@vitel.alcove-fr>
> Since I reported issues about this 3 days ago, I would have appreciated
> being CC:'ed on the patch mail, so I could have reported issues
> like this _before_ such a patch being applied.
BTW, there are atleast 2 dozen people looking for this patch. I tested
it and several others on the linux1394 mailing list tested it. If you
want to be more closely involved with linux1394 specifically, then don't
expect me to search you out...come to us where our development happens.
We have a commit list to the repo and a developers list.
Things happen there...the only reason I bother the general linux-kernel
list is for things that affect outside the scope of drivers/ieee1394/*.
I don't think that's much different than a lot of projects in the
kernel.
I've never sent my patches to the list prior to inclusion in the kernel,
and a lot of folks don't, depending on neccessity. I don't see the need
to start now, not when interested parties have a place to go to see the
patches before hand anyway. Nothing major I send to Marcelo or Linus is
done so without it being committed in out repo first.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-04-26 14:44 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 [this message]
2003-04-26 16:23 ` Stelian Pop
2003-04-26 16:25 ` Ben Collins
2003-04-26 17:15 ` Stelian Pop
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=20030426144017.GD2774@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=stelian.pop@fr.alcove.com \
/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).