Yeah, in retrospect that would probably have been a simpler course to
follow.
I'd be happy to re-work this if you want, but it will probably take a
couple days - the day job needs some attention right now.
On Tue, 25 May 2010, David Young wrote:
On Mon, May 24, 2010 at 08:29:49PM +, Pau
On Mon, May 24, 2010 at 08:29:49PM +, Paul Goyette wrote:
> Module Name: src
> Committed By: pgoyette
> Date: Mon May 24 20:29:49 UTC 2010
>
> Modified Files:
> src/sys/arch/i386/pci: gcscehci.c
> src/sys/dev/cardbus: ehci_cardbus.c ohci_cardbus.c uhci_cardbus.c
> sr
On May 24, 10:32pm, kiyoh...@kk.iij4u.or.jp (KIYOHARA Takashi) wrote:
-- Subject: Re: CVS commit: src/sys/dev/ieee1394
| Hi!
|
|
| From: Izumi Tsutsui
| Date: Mon, 24 May 2010 22:08:21 +0900
|
| > > Why you revert it all?
| >
| > Wasn't it broken?
|
| Yes. It knows I was broken, too. However
> In many cases, there is a case that cannot be fixed in several days. For
In any case you should revert your changes first
if you know you broke the tree and you can't fix it soon.
---
Izumi Tsutsui
Hi!
From: Izumi Tsutsui
Date: Mon, 24 May 2010 22:08:21 +0900
> > Why you revert it all?
>
> Wasn't it broken?
Yes. It knows I was broken, too. However, it worked on my ofppc and
it booted my amd64.
> > I had been investigating the problem of kmem since last week. Was not
>
> There is no
> Why you revert it all?
Wasn't it broken?
> I had been investigating the problem of kmem since last week. Was not
There is no reason to leave kernels broken even if
you have some idea for proper fixes.
You can put them even after you (or other guys) revert
the previous changes, can't you?
---
On May 24, 2:23pm, kiyoh...@kk.iij4u.or.jp (KIYOHARA Takashi) wrote:
-- Subject: Re: CVS commit: src/sys/dev/ieee1394
| Hi! Christos,
|
|
| From: Christos Zoulas
| Date: Sun, 23 May 2010 14:56:59 -0400
|
| > Module Name:src
| > Committed By: christos
| > Date: Sun
