Zach Welch wrote:
> On Thu, 2009-05-07 at 20:26 +0200, Øyvind Harboe wrote:
>   
>> On Thu, May 7, 2009 at 7:18 PM, David Brownell <davi...@pacbell.net> wrote:
>>     
>>> On Thursday 07 May 2009, Øyvind Harboe wrote:
>>>       
>>>> On Thu, May 7, 2009 at 6:38 PM, David Brownell <davi...@pacbell.net> wrote:
>>>>         
>>>>> One of the patches since the merge of the ti_dm355.cfg line-end
>>>>> update seems to have broken some aspect of scan chain discovery.
>>>>> See the openocd server startup transcript below, with "scan_chain"
>>>>> command debug output.  (FWIW, using with an Olimex ft2232 adapter.)
>>>>>           
>>>> Can you do a bisection to figure out which version broke you?
>>>>         
>>> If this were using "git", I'd have done it already ... is the
>>> magic SVN command "svn switch -r REVISION"?  At least there's
>>> only one development sequence, no branch merges to resolve. ;)
>>>       
>> svn will probably do this *MUCH* slower than git with a cloned
>> repository of course, but the syntax is essentially:
>>
>> svn checkout -r N ...
>>
>> http://svnbook.red-bean.com/en/1.0/re04.html
>>     
>
> Everyone thinking about hitting the repository this hard should be sure
> to look into 'svnsync', which allows you to create a read-only copy of
> the repository on your local machine that will be _much_ faster to use.
>
> Cheers,
>
> Zach
>
> _______________________________________________
> Openocd-development mailing list
> Openocd-development@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/openocd-development
>   
Thank you, and I would say the patch from 1606 to 1607 is not valid.

Regards
Magnus

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to