Re: [fpc-pascal] Request for backport to FPC 2.6.1 + wiki page to keep track of backport requests/merges

2012-09-22 Thread Marco van de Voort
In our previous episode, Jonas Maebe said: > >> internal compiler error. > > > > I already had tested it and it applies cleanly. As soon as I get a green > > light from a compiler developer that it is ok to merge, I'll merge it. > > It's ok, thanks. Done, r22436 _

Re: [fpc-pascal] Request for backport to FPC 2.6.1 + wiki page to keep track of backport requests/merges

2012-09-21 Thread Jonas Maebe
On 13 Sep 2012, at 18:22, Marco van de Voort wrote: > In our previous episode, Reinier Olislagers said: >> If possible, I'd like >> r22380 in trunk to be marked for backporting to FPC 2.6.1 as it fixes an >> internal compiler error. > > I already had tested it and it applies cleanly. As soon as

Re: [fpc-pascal] Request for backport to FPC 2.6.1 + wiki page to keep track of backport requests/merges

2012-09-13 Thread Marco van de Voort
In our previous episode, Reinier Olislagers said: > If possible, I'd like > r22380 in trunk to be marked for backporting to FPC 2.6.1 as it fixes an > internal compiler error. I already had tested it and it applies cleanly. As soon as I get a green light from a compiler developer that it is ok to

[fpc-pascal] Request for backport to FPC 2.6.1 + wiki page to keep track of backport requests/merges

2012-09-13 Thread Reinier Olislagers
Hi list, If possible, I'd like r22380 in trunk to be marked for backporting to FPC 2.6.1 as it fixes an internal compiler error. I've created a page on the wiki http://wiki.lazarus.freepascal.org/FPC_2.6.1_fixes_branch that may help keep track of what gets merged/what is on the list for merging.