Re: [Openocd-development] resubmit lost works!

On May 15, 2009, at 11:32 AM, David Brownell wrote: On Thursday 14 May 2009, Zach Welch wrote: If anyone knows of patches that have not been applied, please reply here with a link into the mailing list archives to the last version posted: https://lists.berlios.de/pipermail/openocd-develo

Re: [Openocd-development] resubmit lost works!

Anders Montonen pisze: > It does, but not in an immediately obvious way: >

Re: [Openocd-development] resubmit lost works!

On May 17, 2009, at 11:06, Freddie Chopin wrote: > Zach Welch pisze: >> They should have been treated to 'svn mv', because this would have >> preserved the history available from 'svn log'. > First of all - I've tied to do that this way, but TortoiseSVN does not > offer such option. It does, but n

Re: [Openocd-development] resubmit lost works!

Zach Welch pisze: > They should have been treated to 'svn mv', because this would have > preserved the history available from 'svn log'. First of all - I've tied to do that this way, but TortoiseSVN does not offer such option. Second of all - these are just config files and their history holds

Re: [Openocd-development] resubmit lost works!

On Sat, 2009-05-16 at 16:57 +0200, Øyvind Harboe wrote: > Committed. It took me a while to recognize the fact, but this was a case where the current patch policy fails us badly. r1798 broken the history for all of the files that were moved, because they were removed ('svn rm') and then new copies

Re: [Openocd-development] resubmit lost works!

Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-developmen

Re: [Openocd-development] resubmit lost works!

Øyvind Harboe pisze: Sorry about dropping this on the floor. Could you resubmit the patch against svn head? attached. 4\/3!! Index: src/target/board/crossbow_tech_imote2.cfg === --- src/target/board/crossbow_tech_imote2.cfg (re

Re: [Openocd-development] resubmit lost works!

Sorry about dropping this on the floor. Could you resubmit the patch against svn head? Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@li

Re: [Openocd-development] resubmit lost works!

Zach Welch pisze: > If anyone knows of patches that have not been applied, please reply here > with a link into the mailing list archives to the last version posted: This was ignored a while ago, but if you think that changing that stuff is worthless just tell me (; https://lists.berlios.de/pipe

Re: [Openocd-development] resubmit lost works!

On Fri, 15 May 2009, Øyvind Harboe wrote: > My main reason for wanting patches in attachments is that > I want a *single* format. Forcing attachments help. I'm more > often able to apply those patches than the rest. The Linux process requires a _single_ patch format as well. > In this mailing li

Re: [Openocd-development] resubmit lost works!

On Fri, 15 May 2009, Øyvind Harboe wrote: > > Attachments are annoying, but they avoid lots of odd issues that crop up > > when email clients get too eager to help.  Things like trailing spaces and > > tab to space conversion tends to happen.  Attachments are preserved much > > better in general.

Re: [Openocd-development] resubmit lost works!

On Friday 15 May 2009, Rick Altherr wrote: > Attachments are annoying, but they avoid lots of odd issues that crop   > up when email clients get too eager to help.  Things like trailing   > spaces and tab to space conversion tends to happen.  Attachments are   > preserved much better in general. T

Re: [Openocd-development] resubmit lost works!

> Attachments are annoying, but they avoid lots of odd issues that crop up > when email clients get too eager to help.  Things like trailing spaces and > tab to space conversion tends to happen.  Attachments are preserved much > better in general. If things are leaning towards a bug tracking syste

Re: [Openocd-development] resubmit lost works!

On May 15, 2009, at 11:49 AM, Nicolas Pitre wrote: On Fri, 15 May 2009, David Brownell wrote: I'd also like to see a brief update about why this list adopts the unusual "send as an attachment" policy. Because one of the maintainer uses Windows and applying patches with cut and paste does

Re: [Openocd-development] resubmit lost works!

My main reason for wanting patches in attachments is that I want a *single* format. Forcing attachments help. I'm more often able to apply those patches than the rest. In this mailing list there is also a lot of good contributions from developers who have their first encounter w/svn and patches...

Re: [Openocd-development] resubmit lost works!

On Fri, 15 May 2009, David Brownell wrote: > I'd also like to see a brief update about why this list > adopts the unusual "send as an attachment" policy. Because one of the maintainer uses Windows and applying patches with cut and paste doesn't work so well? FWIW, I consider patches in attachme

Re: [Openocd-development] resubmit lost works!

On Thursday 14 May 2009, Zach Welch wrote: > If anyone knows of patches that have not been applied, please reply here > with a link into the mailing list archives to the last version posted: https://lists.berlios.de/pipermail/openocd-development/2009-May/006282.html but here's a tweaked ve

Re: [Openocd-development] resubmit lost works!

Re: [Openocd-development] resubmit lost works! > > > Generally this is where a bug tracking system comes into play.  Of > > course, as a community, we seem to be against that idea. > > > > This is something that we like to use too keep track of issues. > > > >

Re: [Openocd-development] resubmit lost works!

Hi, -Message d'origine- De : oyvindhar...@gmail.com [mailto:oyvindhar...@gmail.com] De la part de Øyvind Harboe Envoyé : 15 mai 2009 09:15 À : Jonathan Dumaresq Cc : Rick Altherr; openocd-development Objet : Re: [Openocd-development] resubmit lost works! > Generally this is whe

Re: [Openocd-development] resubmit lost works!

-Message d'origine- De : openocd-development-boun...@lists.berlios.de [mailto:openocd-development-boun...@lists.berlios.de] De la part de Rick Altherr Envoyé : 15 mai 2009 02:09 À : Øyvind Harboe Cc : openocd-development Objet : Re: [Openocd-development] resubmit lost works! On M

Re: [Openocd-development] resubmit lost works!

> Generally this is where a bug tracking system comes into play.  Of > course, as a community, we seem to be against that idea. > > This is something that we like to use too keep track of issues. > > It's easy to use and at least, outsider don't have to read all the last > years of email to know wh

Re: [Openocd-development] resubmit lost works!

> Generally this is where a bug tracking system comes into play.  Of course, > as a community, we seem to be against that idea. I think it's a matter of timing and we're nearing the point where it would be *less* work for everybody if we had a bugtracking system. -- Øyvind Harboe Embedded softw

Re: [Openocd-development] resubmit lost works!

On May 14, 2009, at 11:03 PM, Øyvind Harboe wrote: Where do I post bugs that I observe, but have no time to pursue? Here is a bug that I have observed and kinda know the reason for: proc foo{a} { verify_image $a } # this will fail since command.c does not correctly create an overrideabl

Re: [Openocd-development] resubmit lost works!

Where do I post bugs that I observe, but have no time to pursue? Here is a bug that I have observed and kinda know the reason for: proc foo{a} { verify_image $a } # this will fail since command.c does not correctly create an overrideable proc foo c:\\temp\\test.bin #this works verify_image

Re: [Openocd-development] resubmit lost works!

Zach Welch wrote: > Hi all, > > If anyone knows of patches that have not been applied, please reply here > with a link into the mailing list archives to the last version posted: > > https://lists.berlios.de/pipermail/openocd-development/2009-May/006374.html > https://lists.berlios.de/pipe

[Openocd-development] resubmit lost works!

Hi all, If anyone knows of patches that have not been applied, please reply here with a link into the mailing list archives to the last version posted: https://lists.berlios.de/pipermail/openocd-development/ If there are other issues to which the maintainers failed to respond, please con