Am 23.05.2017 um 12:42 schrieb Graeme Geldenhuys:
> On 2017-05-23 11:31, Tomas Hajny wrote:
>> the other, but let me remind you, that it isn't just about Florian. During
>> the previous discussions on this evergreen topic, Florian, Marco, Jonas
>> (if I remember correctly) and others raised quite a few specific questions
>> on how to accomplish particular tasks commonly used in the FPC project. I
>> may have missed something, but I haven't noticed a particular proposal
>> from you or anyone else describing in detail how to cover those needs
> 
> To be honest, I can't actually remember seeing any such proposal (asking for 
> advice or help) in the
> FPC-Users mailing list. Maybe it was in a list I'm not subscribed in? 
> Otherwise, I would have
> happily given my advice.

First problem: quote from core:

Am 05.03.2017 um 20:53 schrieb Jonas Maebe:
> On 05/03/17 14:33, Maciej Izak wrote:
>> Mhm. It hapens also for simplified github import for svn
>> (https://help.github.com/articles/about-github-importer/). My
>> proposition is :
>>
>> git svn init -s http://svn.freepascal.org/svn/fpc
>> :repeatloop
>> git svn fetch
>> If %ErrorLevel%==1 (
>>     Goto :repeatloop
>> )
>>
>> (this command is for repo with all branches, instead of -s I have used
>> for NewPascal --trunk=trunklink but in theory -s should work...)
>
> It doesn't abort with errors (except at some point because we created a 
> branch called "avr", deleted
> it, then again created a branch with that name -- but that can be worked 
> around). It simply does not
> imports some revisions, or does not classify them under the right branches.


But actually, as long as llvm and gcc still use svn, svn should fulfill our 
needs as well :)
_______________________________________________
fpc-other maillist  -  fpc-other@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-other

Reply via email to