On Wed, Dec 16, 2009 at 9:22 PM, Carsten Breuer
<carstenbreueropen...@textwork.de> wrote:
> 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.
> }
No.
- fix a file(including build it)
- commit to local git
Once you're done you can create a patch series and email
it to the list.
You then get some comments, do an interactive rebase
and resubmit the patch list.
> 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.
+ easier for you to rebase.
For a problem like this you *really* need to read up
on maintaining git. I recommend using command line
tools for something like this. TortoiseGit/gui's are almost
certainly the wrong way to go as they are hopelessly far
behind git and tend to try to treat git as svn, which defeats
much of the purpose of using git in the first place.
You will find that learning git(which is a prime example of the
DVCS - distributed version control) will be an excellent investment
of your time in the years to come.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
