On 11/1/10, David Daney <ddaney@xxxxxxxxxxxxxxxxxx> wrote: > On 11/01/2010 12:14 PM, Charles Manning wrote: >> On Tuesday 02 November 2010 07:55:39 David Daney wrote: >>> On 11/01/2010 11:40 AM, Tracey Dent wrote: >>>> The patch sets puts the yaffs2 filesystem in the staging directory. >>>> It is all based on Charles git >>>> tree(http://github.com/cdhmanning/linux-yaffs-integration/). Everything >>>> is compile tested and it builds. >>>> >>>> This only the inital support and I will be sending more cleanup patches. >>>> >>>> Greg can you add the patch set into your staging-next tree. >>>> Also, It doesn't affect anything other than itself. >>>> >>>> Thanks, >>>> >>>> Tracey Dent >>> >>> I am confused. >>> >>> Are you and Charles Manning working together on this? >>> >>> Did you write all this code or did Charles? If it was Charles, why are >>> there no From: and Signed-off-by headers for him? >>> >>> Thanks in advance for enlightening us as to what is going on here, >>> David Daney >> >> We are not working together on this, but I do appreciate the effort in >> helping >> bring to a head what people like/dislike. >> >> I am trying to keep the kernel yaffs consistent with the yaffs.net yaffs >> so >> that it is easier to add changes from yaffs.net. >> > > Great. Thanks for clearing things up. > > I will offer my unsolicited opinion: > > Charles has obviously expended great effort on yaffs2. He has a git > repository hosting the code, and has expressed a desire to get the code > fit for merging. For Tracey Dent to come along and hijack the entire > effort, would anger me if I were in Charles' place. I didn't mean to hijack, I was just trying to help. :( > > Having used yaffs2 in the past, I would like to see the code in the > kernel. Having it come via Charles would seem to make sense. > But regardless it shouldn't matter who submitted the patches, as long as we can get it into mainline. > David Daney > Tracey Dent -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
