Hi folks,
I'm sure many here have read the discussion on lkml about lvm and
the problems that team is having. As part of that discussion it was said:
Dan Kegel <dank@xxxxxxxxx>:
>I know very little about LVM, but from watching earlier projects
>in the same situation you're in now, the path you need to follow
>seems clear:
> Stop using CVS internally for development.
> It makes checking in changes without submitting them to
> Linus too easy.
>To get sync'd back up, *start with the standard kernel*,
>and start generating clean, human-understandable patches one
>at a time that bring it up to where you want.
I am wondering how the XFS team plans on avoiding the same problems once
XFS becomes part of the kernel. Is there potential for problems with SGI
"losing control" over the source or direction of XFS once Linus puts it in
his tree?
How does the above comment relate to the XFS team's plans on patches to
XFS and related areas once XFS is in?
Just want to get these issues into the air before rancor and ill will
spread...
P.S. XFS has been extremely solid and has saved me a lot of time waiting
for fscks. I am really impressed by the professionalism of the XFS team.
Hopefully I can contribute soon - working on a slackware boot/modules/root
disk set for XFS.
James Rich
james.rich@xxxxxxxxxxxxx
|