Hi Brian:
I was thinking, if you're
going to start merging code from udev -> trunk, can you also merge the fixes
from branches/3.6.x -> trunk?
In that case, then trunk will
have all the bugfixes as well as all the new udev + bt stuff.
I would then much rather
spend the time to stabilize trunk than work on fixing up 3.6.x where you already
have the remaining outstanding issues fixed in your udev
branch.
What do you
think?
Cheers,
Bernard
From: Brian Elliott Finley on behalf of Brian Elliott Finley
Sent: Fri 17/02/2006 09:11
To: Bernard Li
Cc: sisuite-devel@lists.sourceforge.net
Subject: Re: modprobe/insmod in 3.6.x
I'm going to start merging my uyok/udev stuff into trunk
today. I'll do
a tag on trunk as pre-merge, just in case the merge
introduces some
instabilities, which it likely will.
May I suggest
that you wait until after my merge?
Cheers, -Brian
Thus spake
Bernard Li ([EMAIL PROTECTED]):
>Hey Brian:
>
>You told me to take
a look at your udev branch for examples on how you use busybox's modprobe/insmod
instead of building them from modutils and module-init-tools.
>
>Do
I need to label my changes with "XXX" such that you won't merge the changes into
trunk as well? But I would imagine there will be a bunch of changes
throughout the entire initrd.rul
file.
>
>Cheers,
>
>Bernard
--
Brian Elliott
Finley
Mobile: 630.631.6621
