Hi Charles,
On Fri, Apr 27, 2012 at 8:59 AM, Charles Manning manningc2@actrix.gen.nz wrote:
On Friday 27 April 2012 00:25:55 Wolfgang Denk wrote:
Dear Charles Manning,
In message 201204261028.44543.manningc2@actrix.gen.nz you wrote:
yaffs went through a large reformat a while ago meaning that the current code does not diff well against the old code. Future changes shuld be a lot easier to handle with direct patching.
yaffs changes typically don't go through the yaffs list since people with direct git checkin access do 95-99% of the changes.
U-Boot has a different policy. Here nothing goes into mainline that has not been posted on the mailing list before. There are several reasons for this: 1) We want to make sure that the code has actually been visible and reviewed. When pulling from a git repo, you just get a drop of software in unknown condition. 2) We want to make sure the review process gets recorded - we use patchwork for this purpose.
So if you want to submit your code, then please post patches. There is no way around this step.
I understand what you are trying to achieve but the reality is that nobody is going to read the patching of a whole file system.
If you supported patches greater than 100k this would be trivial to do, but I have a single file greater than that. Perhaps it is time to accept larger patches more consistent with the lkml and friends.
We do support patches > 100k - Just not directly via the mailing list. They get posted here:
http://www.denx.de/wiki/view/U-Boot/TooBigPatches
You will need to set yourself up on the U-Boot wiki to post your patches there
Regards,
Graeme