From: Ben Collins <bcollins@debian.org>
To: Bill Fink <billfink@mindspring.com>
Cc: Linux IEEE1394 Developers <linux1394-devel@lists.sourceforge.net>,
LinuxPPC Developers <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Firewire Disk Broken in 2.4.19-pre8-ben0 kernel (was working fine with 2.4.18-ben0)
Date: Mon, 13 May 2002 11:13:19 -0400 [thread overview]
Message-ID: <20020513151319.GI494@blimpo.internal.net> (raw)
In-Reply-To: <20020513105519.7cb1daf8.billfink@mindspring.com>
> ohci1394: $Revision: 1.101 $ Ben Collins <bcollins@debian.org>
Try the SVN code base (check the website for how to download).
--
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-13 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 14:55 Firewire Disk Broken in 2.4.19-pre8-ben0 kernel (was working fine with 2.4.18-ben0) Bill Fink
2002-05-13 15:13 ` Ben Collins [this message]
2002-05-13 16:07 ` Bill Fink
2002-05-13 16:09 ` Ben Collins
2002-05-13 17:29 ` benh
2002-05-14 4:40 ` Bill Fink
2002-05-14 5:57 ` Michel Lanners
2002-05-14 13:09 ` Ben Collins
2002-05-15 2:49 ` Bill Fink
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=20020513151319.GI494@blimpo.internal.net \
--to=bcollins@debian.org \
--cc=billfink@mindspring.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.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).