Hi Øyvind,
>> OK, then i will start to fix all the mallocs that are handled not
>> correct yet and where i understand what to do if they fail.
> Great! I think if you do a pass on the *simple* cases and just mark
> w/todo on the remaining ones that would be *great*. I think it makes
> sense to split this into many commits. Minimally one per file. I take
> it you are familiar with how to create a patch series?
I know it in subversion, but not in git.
I would do the following:
for number_of_mallocs:
{
- fix the file
- see if it compiles.
- create a patch
- send it too you.
}
Is there any windows client that you can suggest?
Something like TortoiseGIT?
> Focus on a handful of malloc()'s just ot get the procedure right
> w.r.t. committing to git, submitting patches, etc.
Yes, smaller commits are better and easier to merge. agreed.
>> Start with the obviously broken and move down the list...
OK.
Best Regards,
Carsten
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
