Hi Andreas and all,
Thanks again, I will keep your notes handy.
Cheers.
On Mon, Oct 7, 2013 at 4:06 PM, Andreas Fritiofson <
andreas.fritiof...@gmail.com> wrote:
>
> On Mon, Oct 7, 2013 at 11:51 PM, Nader <nsheha...@gmail.com> wrote:
>
>> Hi Guys,
>>
>> EUREKA! It worked like a charm :)
>>
>
> I'm glad to hear!
>
>
>> Unfortunately not familiar how to fetch the patch by itself, so i went
>> ahead carried the changes manually to my src/flash/nor/stm32f2x.c ,
>> compiled and built again my .exe and tried it out. All worked out fine
>> (output below). I am afraid I have to count on you guys to file the bug and
>> fixes in Gerrit if needed, I am not familiar with the process, unless you
>> can throw me some tips how to fetch the patch itself etc...
>>
>
> You've posted the results here. The patch is already in Gerrit, build
> tested, reviewed, approved and should be merged to the SF repo in a few
> days. So you don't need to do anything more.
>
> If you need to get involved in the future, it's rather easy though; just
> log in to the Gerrit page using any OpenID provider (your Gmail ID will do
> fine). Find the patch, click Review to post feedback and that's it.
> Contributing your own patches are similarly easy if you're used to basic
> git operations.
>
> For info, the command to run to get the patch is printed in Gerrit (the
> link I provided) under Download/checkout -> "git fetch
> http://openocd.zylin.com/openocd refs/changes/89/1689/1 && git checkout
> FETCH_HEAD" and is meant to be run in a clean git working tree.
>
>
>> I usually use "git clone git://git.code.sf.net/p/openocd/codeopenocd-code"
>> in my $cygwin home folder and it downloads the package and
>> everything needed.
>>
>
> "Usually"? You should only need to do that once...
>
>
>> I just noticed that the master on SF is not yet updated with the changes.
>>
>
> We usually allow for a week or so in the Gerrit review system before
> submitting changes. Sometimes shorter for trivial bugfixes like this.
>
>
>> Thanks again for everything, looking fwd for the next official release.
>>
>
> Unfortunately, that might take a while, No-one have started planning a
> 0.8.0 release yet, as far as I know. You'll have to build your own until
> then. But if you're using new hardware, you'll probably want to run latest
> git anyway. Releases go stale pretty quickly, due to bugs like this.
>
> Regards,
> Andreas
>
--
Nader Shehayed
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
