So that's normal that all patchsets now are marked as "not verified"
("X") because the build fails at a file completely unaffected by that
patch and unchanged for a long time (buspirate.c for example)?
4\/3!!
___
Openocd-development mailing list
Openo
The change that Steve Bennett suggested me in email is now posted to
Gerrit and it solves the problem.
> uplevel #0 [list source [find $filename]]
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.d
On Sat, Oct 22, 2011 at 10:03 AM, Freddie Chopin wrote:
> So that's normal that all patchsets now are marked as "not verified" ("X")
> because the build fails at a file completely unaffected by that patch and
> unchanged for a long time (buspirate.c for example)?
I'm still picking out the nits of
On Sat, Oct 22, 2011 at 10:03 AM, Freddie Chopin wrote:
> So that's normal that all patchsets now are marked as "not verified" ("X")
> because the build fails at a file completely unaffected by that patch and
> unchanged for a long time (buspirate.c for example)?
"all" you have to do, is to rebas
On 2011-10-22 10:50, Øyvind Harboe wrote:
"all" you have to do, is to rebase your fix on top of the other fix
that's in the
queue and push. Then your patch will go green.
Hmm... Something not working on the server probably...
$ git fetch http://openocd.zylin.com/p/openocd refs/changes/43/43/3
Could someone try this on OpenOCD and report back?
I'd like to see this run on the Jenkins server so that we can be sure
that we run with the minimum # of includes.
Reducing the # of includes is good from an architectural point of
view to reduce cohesion between parts of the system.
--
Øyvind H
>> $ git fetch http://openocd.zylin.com/p/openocd refs/changes/43/43/3 && git
>> checkout FETCH_HEAD
>> error: RPC failed; result=22, HTTP code = 503
>> fatal: The remote end hung up unexpectedly
>
> Anyway - I see that my patch depends now on buspirate fix, so I guess that
> is't done.
I did it t
Hi!
Would it be possible to move the gerrit emails to another list? Like
openocd-gerrit, or something?
I would be very interested in the development discussions on the lists
however the gerrit commits are "spamming" the real emails.
I use gmail, and it's not possible to create a filter that would
Hi!
Changing the reset config to separate, and the script to use "reset
halt" worked, now every programming works!
Here's my output. http://sem.sch.bme.hu/~akos/output.txt It was
created using reset_config trst_pulls_srst and "reset run".
If it is any help I can send the output using the fixed
This is an automated email from Gerrit.
Antonio Borneo (borneo.anto...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/50
-- gerrit
commit b276d6e9eeacf7b7c863c6212ae2a883eb0be09d
Author: Antonio Borneo
Date: Sat Oct 22 19:23:10 2011 +0800
Hi guys,
I'd like to thank everybody that has helped make the new patch
procedure a success so far.
I would like to make a clean scan-build a requirement for "verified"
on all submitted patches and we have ca. 30 or so minor nits
fix before this is the case.
Procedure:
- Search for "warning" be
Thanks Peter. I will wait for his reply.
Thanks for the info about the versaloon debugger. I will definitely keep it
in mind for my next dongle purchase.
-Ananda
On Fri, Oct 21, 2011 at 6:08 PM, Peter Stuge wrote:
> Hi Ananda,
>
> Ananda Regmi wrote:
> > Does anybody here know if Amontec - mak
This is an automated email from Gerrit.
Mathias K?ster (kes...@freenet.de) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/51
-- gerrit
commit cb685c9f575047b8f0a4853069e775c4f0052498
Author: Mathias K
Date: Sat Oct 22 18:00:20 2011 +0200
add Free
13 matches
Mail list logo
