Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-26 Thread Marco van de Voort via fpc-devel 


Op 25-10-2021 om 13:06 schreef LacaK via fpc-devel:
The base output  is starting to work somewhat. 
http://www.stack.nl/~marcov/mergelogs32/restset.html
Marco, can I see what commits were already merged ? (and what not - 
iow what is candidate for merging)


I don't really maintain lists of what was merged, only what was 
candidate for merge(*)


Basically, it just finds all eligible revs using the "merging" repo 
script, and then sorts that over categories, with a "rest" category for 
not yet categorized revs, and a "all" category for all revs. Which revs 
are in which categories is maintained by a simple ini file.


All category files are in html (more dense easier to read) and in .txt 
(easier to grep) format.


The main index lists all categories: 
http://www.stack.nl/~marcov/mergelogs32/


with the "rest" set being the last one. You are most probably interested 
in the "Database" subcategory:


http://www.stack.nl/~marcov/mergelogs32/fcl-db.html

http://www.stack.nl/~marcov/mergelogs32/fcl-db.txt

These are _NOT_ yet complete, some fixes to database headers are not in 
them yet. I still have a lot of the revisions from july till now to 
categorize.


but beware,  such files consists out two parts. Revisions that are 
eligible (first part), and revisions that were eligible and categorized, 
but have been merged meanwhile (second part after "(inactive) Revisions 
in this set" header).


I can do three levels of grep on this. Only on the "rest" set, which is 
the common mode, to see which new files in some category (e.g. "fcl-db/" 
) there are.


To resolve conflicts I can also search on all eligible revisions with 
the option to exclude some revision sets that contain very large files 
(very large branches merged in, and makefile regen end up there, because 
they touch many files and often grep while being non relevant.


(*) In theory, you could find out by checking what is eligible of the 
last release branch, and subtracting the eligible of the fixes branch 
from it, but I don't know yet how to do that in git.  It is also not 
perfect, there will be some pollution with e.g. version update commits.


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-25 Thread LacaK via fpc-devel 
The base output  is starting to work somewhat. 
http://www.stack.nl/~marcov/mergelogs32/restset.html
Marco, can I see what commits were already merged ? (and what not - iow 
what is candidate for merging)

L.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-25 Thread Marco van de Voort via fpc-devel 


Op 24-10-2021 om 18:13 schreef Marco van de Voort via fpc-devel:


When you have a hash, you can translate it in a "relative" revision 
number by:


git describe  | sed -nr 's/.*-(.*)-.*/\1/p'

It is basically the number of commits after the last annotation tag 
(3.3.1 in case of main).


I have the date field in the revisions, so that is not so much of a 
problem. But due to historic reasons, the program does set logic with 
stringlists of only SVN revs, and only fetches logs and other meta 
data later. So just the order of things has to change completely.


Not fundamental, just a lot of rearranging.

The base output  is starting to work somewhat. 
http://www.stack.nl/~marcov/mergelogs32/restset.html


In some output there is still a 'r' before revs, and the header parts 
(rev/date/author) are not yet nicely folded yet, making the HTML output 
less concise, but that is only makeup, I'll clean this up bit by bit.


More important is getting the actual set logic (show all uncategorized 
commits matching "fcl-pascal/" ) working again.


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-24 Thread Marco van de Voort via fpc-devel 


Op 24-10-2021 om 17:52 schreef Florian Klämpfl via fpc-devel:


This week I've been working on getting the merge logs etc working 
again. Things are showing info again, but sorting is broken (since 
you can't simply sort the revs anymore).


When you have a hash, you can translate it in a "relative" revision 
number by:


git describe  | sed -nr 's/.*-(.*)-.*/\1/p'

It is basically the number of commits after the last annotation tag 
(3.3.1 in case of main).


I have the date field in the revisions, so that is not so much of a 
problem. But due to historic reasons, the program does set logic with 
stringlists of only SVN revs, and only fetches logs and other meta data 
later. So just the order of things has to change completely.


Not fundamental, just a lot of rearranging.


Thx for the merges

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-24 Thread Florian Klämpfl via fpc-devel 

Am 24.10.21 um 16:52 schrieb Marco van de Voort via fpc-devel:


Op 24-10-2021 om 14:09 schreef Florian Klämpfl via fpc-devel:


Am 10.10.2021 um 15:55 schrieb Florian Klämpfl via fpc-devel 
:


Reminder :)

So far I have only the second avr merge list from Christo open. 
Anything else?

Next reminder, meanwhile, I merged the avr stuff.


This week I've been working on getting the merge logs etc working again. 
Things are showing info again, but sorting is broken (since you can't 
simply sort the revs anymore).


When you have a hash, you can translate it in a "relative" revision 
number by:


git describe  | sed -nr 's/.*-(.*)-.*/\1/p'

It is basically the number of commits after the last annotation tag 
(3.3.1 in case of main).




Anyway, I grepped on my name, and found these:

622554b59fe19bf0ff1dcf18c1106db960305ef6
84507b49c217cf6cd37023a79c1cff075bb3cb03


"Merged".
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-24 Thread Marco van de Voort via fpc-devel 


Op 24-10-2021 om 14:09 schreef Florian Klämpfl via fpc-devel:



Am 10.10.2021 um 15:55 schrieb Florian Klämpfl via fpc-devel 
:

Reminder :)

So far I have only the second avr merge list from Christo open. Anything else?

Next reminder, meanwhile, I merged the avr stuff.


This week I've been working on getting the merge logs etc working again. 
Things are showing info again, but sorting is broken (since you can't 
simply sort the revs anymore).


Anyway, I grepped on my name, and found these:

622554b59fe19bf0ff1dcf18c1106db960305ef6
84507b49c217cf6cd37023a79c1cff075bb3cb03

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-24 Thread Florian Klämpfl via fpc-devel 


> Am 10.10.2021 um 15:55 schrieb Florian Klämpfl via fpc-devel 
> :
> 
> Reminder :)
> 
> So far I have only the second avr merge list from Christo open. Anything else?

Next reminder, meanwhile, I merged the avr stuff.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-03 Thread Christo Crause via fpc-devel 
On Fri, Oct 1, 2021 at 11:03 PM Christo Crause 
wrote:

> On Wed, Sep 29, 2021 at 8:42 PM Florian Klämpfl via fpc-devel <
> fpc-devel@lists.freepascal.org> wrote:
>
>> Am 29.09.21 um 18:10 schrieb Christo Crause via fpc-devel:
>> > There is a long list of AVR commits dating back to 2018.  Is someone
>> > looking at this, or should I prepare a list?
>>
>> Not yet, if you can provide one, that would be great!
>>
>
Below a second list of commits for AVR & embedded:

2d9cdab264fc77bc72298006df1621c28a5cb426
28391e04bcf54a5acfddb0f2efe5bcc5614ac4c5
bd96765632bc483c84ed58debfecedcf393ad3b6
429130fa344907371a085ae623791535cb4b101a
ae8d2dc69a518eac8950ae09f45061802cda99ee
08c2afb0a42ba236098d73f72e522085cd07bba2
3ab8830b83b461b590340ad8592050a6a587d74f
d2a059bd02887993320d4177bc5502b22f83fd56
17c4834a4af3993728c8950b4e41bb77b5a34a93
670c61e7609d02e978a6b0b7f26effdc132a1840
7892e3f7b788c2456a2c8f1e0aef35647d1f
9d91d680fbe877215de88cd898003c7c134d730a
00214406bc108fd4b9f08b28a412cfb2d3442924
7d283f530ecd1ddb80e8b89649f30be7dd56a0ba
36058ca4d441c88b4ddac39de72976cca6560ecd
640fe9c29095d8f2e7f928bf3f775e151173309c
4fe21a8e1a1d5e12ae795ac1f17558d5d55cdf77
e033269deb80e1bf923d26fbee2bd2170bc660cf
5040e31f1164afb3ed60b1cbf98d5f34467ebaf2
04ad607bb43c0508d51c60f88b702b25a339abaa
925979c6e47a9e665d804cb75b5a9b73a534b048
dea63e3d613507fb4e9eb6849a5882c4d62bfa48
a905a074b0c475a8202436547bd02963764cdbcc
297d6e2c60d44a2ded0affad4593f3bff3d5b384
84cfa8d9b0140def94a4caeb8c35fbd6ec395c20
2135b9b724549e4c6b8fc8b5472b098539e1a9bf
fd4fb5fa192b149d7f5c33d1820eca00af8430e1
0424c2a658c5bdad38adf30445ad86b8406e42cb
fc50edfe31d0c1a6df9461a7ca183253be142199
599b7e80c022ede41935ddee2680ccc63de88ef9
37a3b542e6d2498d0160f29f4b0e84575aa7ef3e
b8c707ed7ec518f89df8d3853615a2b556b2fd78
fa543359380db005b6fe48a3cd02df6ba31fa405
eb098a3d116984e3c2fb2ca35e039f060efe8550
3482121831a899c3acf0a8f2d0e2d8e401a2eda5
6d75992674a3f7818195507d9cae1fbc8370c10f
98a748bdd6e3220c299e6cfcbdd64d92e1b335a3
5e1e6c24a48a41549d7293f18fb04805adbc5570
9bfc731bb6722eb6d66391515bcb452fee104f40
9d6ceda532a226c1dfa7a8c110c84fbdc57f1971
aec49340a3f18aeab4204375fa1d6d18c6a59422
89a961f960e8cf2cafc013c31f3a02564bdcd13e
9926eb8dc617931f174afa2106b10bc7467fedf2
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-03 Thread Christo Crause via fpc-devel 
On Sat, Oct 2, 2021 at 10:53 PM Dimitrios Chr. Ioannidis <
d.ioanni...@nephelae.eu> wrote:

> I think that the CIE dwarf fix should be included also, commit
> 1e960a9aeb12ae75877ef9321efbb89f34bbbdce .
>
Even though that particular commit is simple, it is entangled with commit
65aebd22b0cb4e170964819b3e439f0799ca9138 (eh_frame based exception
handling) which isn't part of the eligible commits.  It is possible to
replace line 370 in fixes_3_2 (tc:=tai_const.create_sym(cielabel);) with
tc:=tai_const.create_type_sym(aitconst_32bit,cielabel), unfortunately I
don't have a test case to check if this still work as expected.  Perhaps
Florian can check?
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-02 Thread Dimitrios Chr. Ioannidis via fpc-devel 

Hi,

Στις 2/10/2021 12:03 π.μ., ο/η Christo Crause via fpc-devel έγραψε:
On Wed, Sep 29, 2021 at 8:42 PM Florian Klämpfl via fpc-devel 
> wrote:


Am 29.09.21 um 18:10 schrieb Christo Crause via fpc-devel:
> There is a long list of AVR commits dating back to 2018.  Is
someone
> looking at this, or should I prepare a list?

Not yet, if you can provide one, that would be great!


Below is a list of commits that kind of merge relatively easily.  This 
covers most of the relevant AVR patches up to Jan 2020, just before 
the avrtiny support was added.  There are three commits in this period 
that rely on more invasive and widespread changes of other commits, I 
will list them separately at the end.


 

I think that the CIE dwarf fix should be included also, commit 
1e960a9aeb12ae75877ef9321efbb89f34bbbdce .


regards.

--

Dimitrios chr. Ioannidis

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-02 Thread Florian Klämpfl via fpc-devel 
 
>> 
>> Problematic - seems to require commits that affect other targets:
>> 8fd0a27875abb2636a1388876f590a3a56d83b56 - commit doesn't compile, missing 
>> definition of labelcnt
>> ae04e5d7f0c2527677b7c4ce6be2c235a4635c82 - doesn't compile, requires 
>> definition of TransferUsedRegs in 94d7a02fae1d06a40fc9313f7e42323f97d577c7 
>> but that doesn't merge cleanly (conflicts in aoptx86.pas).
>> 4b4e316af02a968f27147123b189b04a9931ba79 - requires commit or fix that 
>> renames FPC_in_cpu_first to in_cpu_first
> 
> If they do not fix really important things, then I would leave them out.
> 
> There are a couple of refactoring commits in the aopt units that seem like 
> general improvements (e.g. 94d7a02fae1d06a40fc9313f7e42323f97d577c7) which 
> haven't been picked yet.  Will these be merged at some point, maybe 3.4?

3.4 will be branched from main so these changes will be there for sure.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-02 Thread Christo Crause via fpc-devel 
On Sat, Oct 2, 2021 at 7:42 PM Florian Klämpfl via fpc-devel <
fpc-devel@lists.freepascal.org> wrote:

>
>
> Am 01.10.2021 um 23:03 schrieb Christo Crause via fpc-devel <
> fpc-devel@lists.freepascal.org>:
>
> Below is a list of commits that kind of merge relatively easily.  This
> covers most of the relevant AVR patches up to Jan 2020, just before the
> avrtiny support was added.  There are three commits in this period that
> rely on more invasive and widespread changes of other commits, I will list
> them separately at the end.
>
>
> Thanks, applied.
>
>
> I needed also
>
> f92b8d1681c0d1ca2228b3114373085524cd93ff
>

Indeed, apologies for missing that one.


>
> Problematic - seems to require commits that affect other targets:
> 8fd0a27875abb2636a1388876f590a3a56d83b56 - commit doesn't compile, missing
> definition of labelcnt
> ae04e5d7f0c2527677b7c4ce6be2c235a4635c82 - doesn't compile, requires
> definition of TransferUsedRegs in 94d7a02fae1d06a40fc9313f7e42323f97d577c7
> but that doesn't merge cleanly (conflicts in aoptx86.pas).
> 4b4e316af02a968f27147123b189b04a9931ba79 - requires commit or fix that
> renames FPC_in_cpu_first to in_cpu_first
>
>
> If they do not fix really important things, then I would leave them out.
>

There are a couple of refactoring commits in the aopt units that seem like
general improvements (e.g. 94d7a02fae1d06a40fc9313f7e42323f97d577c7) which
haven't been picked yet.  Will these be merged at some point, maybe 3.4?
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-02 Thread Florian Klämpfl via fpc-devel 


> Am 01.10.2021 um 23:03 schrieb Christo Crause via fpc-devel 
> :
> 
> On Wed, Sep 29, 2021 at 8:42 PM Florian Klämpfl via fpc-devel 
> mailto:fpc-devel@lists.freepascal.org>> 
> wrote:
> Am 29.09.21 um 18:10 schrieb Christo Crause via fpc-devel:
> > There is a long list of AVR commits dating back to 2018.  Is someone 
> > looking at this, or should I prepare a list?
> 
> Not yet, if you can provide one, that would be great!
> 
> Below is a list of commits that kind of merge relatively easily.  This covers 
> most of the relevant AVR patches up to Jan 2020, just before the avrtiny 
> support was added.  There are three commits in this period that rely on more 
> invasive and widespread changes of other commits, I will list them separately 
> at the end.

Thanks, applied.

> 
> 42e54c1ad5262f0954375c9e40fa4cc8cc32ab7c
> 917de001d6af01c4d3f11a6ddfe59935ee859a8f
> 8fceba449334735be058a1db4dbf1d8c5f999046
> 12879adc2f370c6bbdaa8dd2e0b80a0174ddb82b
> 3ad450c6364e471810e008a2bf13b1e48b4d849b
> c867d2b7f64b4fe56c923924c40199447512dc48
> 009c87156a1ca1f2eb6b08f7bc01e0e7816eb13c
> 2f501be2a0a17091460c8307862671cb9dbff45b
> 5bdc635f50c284217c336a407da774c6850a7f9e
> dee01978907bf4ae544fe53c95a81cea34f1ce4d
> aa4961d06e12c43a802ee25305d8805cf1ff1414
> ee7bc1d5165d96fce1437d625b29649b0c95b322
> 0d97dc7965dd95f7b44692d57851aca0db2894dd
> 48a7c0989a8858737ecc18fc62f237753d1d05c9
> 030cf78ac58eadfe491877676d8a5a51844514c5
> ff3372567f16be75ed1762f3fd5b302faa5e12d6
> 4b93eb64b314ef1c127156b17da59bbba14bc13d
> 893507a5d6b0fbd28568154fbf63d6053fefbc1a
> 91016c97a43192836780f6bd5b1c0da01f1d4b6b
> f72342ed0e7e2c4e268de982a64222dcdc3d75af
> 1b698d319fd2f30ea9314b18063f9f64c1cf23c5
> 9e5cbce6be0c5658610ab93e1f193ef7cc289f7f
> 05c4f45596c7605a5c1801ae86efd86a1a006d18
> 4e93a9a6c7ad4eac2ec416f724013dd4a0860cf2
> dd2d1bf68b5c85c66a1d59b2f1d2319cb3b726af
> 5fc12500f277327255e011decd672285b71892c7
> 3b1903b43056f112b340c878699dbf7f80b16ded
> f61207f1cc24fd547353895c8b83154527b0be64
> e8a48be3bcc50859231ef4550e43f9f677164155
> 701848889e58254c7925415dee7212ff655b6264
> fabe4cc0676679fde2b8d888dd81b902eed4b3be
> 6f434b6751b2fb4f459e5f004086c6ede5436309
> 96a4cda03b66fc568b5e6bc1421e9465b772b594
> aaa6ae5770d07ee28be4e17ba331f45d940bb6bd
> 26eae3672ba6b5981d7a473094d7d22815b359b0
> f629fa1bb9760e2dc2b0ee9761b0c52bf76b4fa7

I needed also

f92b8d1681c0d1ca2228b3114373085524cd93ff

> 
> Problematic - seems to require commits that affect other targets:
> 8fd0a27875abb2636a1388876f590a3a56d83b56 - commit doesn't compile, missing 
> definition of labelcnt
> ae04e5d7f0c2527677b7c4ce6be2c235a4635c82 - doesn't compile, requires 
> definition of TransferUsedRegs in 94d7a02fae1d06a40fc9313f7e42323f97d577c7 
> but that doesn't merge cleanly (conflicts in aoptx86.pas).
> 4b4e316af02a968f27147123b189b04a9931ba79 - requires commit or fix that 
> renames FPC_in_cpu_first to in_cpu_first

If they do not fix really important things, then I would leave them out.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-10-01 Thread Christo Crause via fpc-devel 
On Wed, Sep 29, 2021 at 8:42 PM Florian Klämpfl via fpc-devel <
fpc-devel@lists.freepascal.org> wrote:

> Am 29.09.21 um 18:10 schrieb Christo Crause via fpc-devel:
> > There is a long list of AVR commits dating back to 2018.  Is someone
> > looking at this, or should I prepare a list?
>
> Not yet, if you can provide one, that would be great!
>

Below is a list of commits that kind of merge relatively easily.  This
covers most of the relevant AVR patches up to Jan 2020, just before the
avrtiny support was added.  There are three commits in this period that
rely on more invasive and widespread changes of other commits, I will list
them separately at the end.

42e54c1ad5262f0954375c9e40fa4cc8cc32ab7c
917de001d6af01c4d3f11a6ddfe59935ee859a8f
8fceba449334735be058a1db4dbf1d8c5f999046
12879adc2f370c6bbdaa8dd2e0b80a0174ddb82b
3ad450c6364e471810e008a2bf13b1e48b4d849b
c867d2b7f64b4fe56c923924c40199447512dc48
009c87156a1ca1f2eb6b08f7bc01e0e7816eb13c
2f501be2a0a17091460c8307862671cb9dbff45b
5bdc635f50c284217c336a407da774c6850a7f9e
dee01978907bf4ae544fe53c95a81cea34f1ce4d
aa4961d06e12c43a802ee25305d8805cf1ff1414
ee7bc1d5165d96fce1437d625b29649b0c95b322
0d97dc7965dd95f7b44692d57851aca0db2894dd
48a7c0989a8858737ecc18fc62f237753d1d05c9
030cf78ac58eadfe491877676d8a5a51844514c5
ff3372567f16be75ed1762f3fd5b302faa5e12d6
4b93eb64b314ef1c127156b17da59bbba14bc13d
893507a5d6b0fbd28568154fbf63d6053fefbc1a
91016c97a43192836780f6bd5b1c0da01f1d4b6b
f72342ed0e7e2c4e268de982a64222dcdc3d75af
1b698d319fd2f30ea9314b18063f9f64c1cf23c5
9e5cbce6be0c5658610ab93e1f193ef7cc289f7f
05c4f45596c7605a5c1801ae86efd86a1a006d18
4e93a9a6c7ad4eac2ec416f724013dd4a0860cf2
dd2d1bf68b5c85c66a1d59b2f1d2319cb3b726af
5fc12500f277327255e011decd672285b71892c7
3b1903b43056f112b340c878699dbf7f80b16ded
f61207f1cc24fd547353895c8b83154527b0be64
e8a48be3bcc50859231ef4550e43f9f677164155
701848889e58254c7925415dee7212ff655b6264
fabe4cc0676679fde2b8d888dd81b902eed4b3be
6f434b6751b2fb4f459e5f004086c6ede5436309
96a4cda03b66fc568b5e6bc1421e9465b772b594
aaa6ae5770d07ee28be4e17ba331f45d940bb6bd
26eae3672ba6b5981d7a473094d7d22815b359b0
f629fa1bb9760e2dc2b0ee9761b0c52bf76b4fa7

Problematic - seems to require commits that affect other targets:
8fd0a27875abb2636a1388876f590a3a56d83b56 - commit doesn't compile, missing
definition of labelcnt
ae04e5d7f0c2527677b7c4ce6be2c235a4635c82 - doesn't compile, requires
definition of TransferUsedRegs in 94d7a02fae1d06a40fc9313f7e42323f97d577c7
but that doesn't merge cleanly (conflicts in aoptx86.pas).
4b4e316af02a968f27147123b189b04a9931ba79 - requires commit or fix that
renames FPC_in_cpu_first to in_cpu_first
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-29 Thread Florian Klämpfl via fpc-devel 

Am 29.09.21 um 15:19 schrieb Gabor Boros via fpc-devel:

2021.09.26. 10:42 keltezéssel, Florian Klämpfl via fpc-devel írta:
To do so, some stuff from main (former trunk) might need to be merged 
as well as regressions against 3.2.2 need to be fixed.



Florian,

f6e6b807d5db9adaebd4f17f83b331bed1e09399 (https://lists.freepascal.org 
pipermail/fpc-pascal/2020-July/058287.html)


Fixed in trunk earlier but 3.2.2 still slow. Can you backport the fix to 
fixes_3_2 or is not an easy task?




It is more a question of philosophy: it is not really a fix of a 
regression or any other serious bug. So I prefer not to do so expect if 
you tell me, lazarus is running 10 times slower than needed due to this ;)

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-29 Thread Florian Klämpfl via fpc-devel 

Am 28.09.21 um 08:07 schrieb LacaK via fpc-devel:

Thank you!
Will there be also https://wiki.freepascal.org/FPC_New_Features_3.2.4 ?
(I would like add there note)


Now there is one ;)
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-29 Thread Florian Klämpfl via fpc-devel 

Am 29.09.21 um 18:10 schrieb Christo Crause via fpc-devel:
On Sun, Sep 26, 2021 at 10:42 AM Florian Klämpfl via fpc-devel 
mailto:fpc-devel@lists.freepascal.org>> 
wrote:


A log of not yet considered commits can be found at
https://gitlab.com/freepascal.org/fpc/merging/-/blob/main/eligible.log



There is a long list of AVR commits dating back to 2018.  Is someone 
looking at this, or should I prepare a list?


Not yet, if you can provide one, that would be great!
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-29 Thread Christo Crause via fpc-devel 
On Sun, Sep 26, 2021 at 10:42 AM Florian Klämpfl via fpc-devel <
fpc-devel@lists.freepascal.org> wrote:

> A log of not yet considered commits can be found at
> https://gitlab.com/freepascal.org/fpc/merging/-/blob/main/eligible.log
>

There is a long list of AVR commits dating back to 2018.  Is someone
looking at this, or should I prepare a list?
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-29 Thread Gabor Boros via fpc-devel 

2021.09.26. 10:42 keltezéssel, Florian Klämpfl via fpc-devel írta:
To do so, some stuff from main 
(former trunk) might need to be merged as well as regressions against 
3.2.2 need to be fixed.



Florian,

f6e6b807d5db9adaebd4f17f83b331bed1e09399 (https://lists.freepascal.org 
pipermail/fpc-pascal/2020-July/058287.html)


Fixed in trunk earlier but 3.2.2 still slow. Can you backport the fix to 
fixes_3_2 or is not an easy task?


Gabor
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-29 Thread Ladislav Karrach via fpc-devel 




Thank you!
Will there be also https://wiki.freepascal.org/FPC_New_Features_3.2.4 ?

Sorry it should be: https://wiki.freepascal.org/User_Changes_3.2.4
L.

(I would like add there note)
L.



Am 27.09.2021 um 08:47 schrieb LacaK via fpc-devel 
:


Hello,


Sorry for so long list,
No problem, a list is probably much easier to use than the web 
interface.


I cherry picked all mentioned commits into fixes.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel



___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-28 Thread LacaK via fpc-devel 

Thank you!
Will there be also https://wiki.freepascal.org/FPC_New_Features_3.2.4 ?
(I would like add there note)
L.




Am 27.09.2021 um 08:47 schrieb LacaK via fpc-devel 
:

Hello,


Sorry for so long list,

No problem, a list is probably much easier to use than the web interface.

I cherry picked all mentioned commits into fixes.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread Florian Klämpfl via fpc-devel 


> Am 27.09.2021 um 08:47 schrieb LacaK via fpc-devel 
> :
> 
> Hello,
> 
> 
> Sorry for so long list,

No problem, a list is probably much easier to use than the web interface.

I cherry picked all mentioned commits into fixes.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread LacaK via fpc-devel 



Dňa 27.9.2021 o 14:13 Michael Van Canneyt napísal(a):



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:


And I get then redirect to:
https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-a8cd770b_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964 





That's strange because it should again go to the free pascal project. 
What target project did you choose ?


Pick into project = freepascal.org/fpc/source
Pick into branch = fixes_3_2


Looking at the URL, I doubt this, see my other mail.
But maybe indeed some redirect happened after your initial choice, this 
I cannot see

of course.



Step by step:
1. I am here in commit: 
https://gitlab.com/freepascal.org/fpc/source/-/commit/b5a1c93ec282cedd9aa14c384e913c73ab9c087c

2. Click on Options/Cherry-pick
3. Select  Pick into project = freepascal.org/fpc/source and Pick into 
branch = fixes_3_2

4. Click Cherry-pick button
5. I get another error message: "Sorry, we cannot cherry-pick this 
commit automatically. This commit may already have been cherry-picked, 
or a more recent commit may have updated some of its content."


Let it be ...
L.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread Michael Van Canneyt via fpc-devel 



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:

And I get then redirect to: 

https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-a8cd770b_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964 




That's strange because it should again go to the free pascal project. 
What target project did you choose ?


Pick into project = freepascal.org/fpc/source
Pick into branch = fixes_3_2


Looking at the URL, I doubt this, see my other mail.
But maybe indeed some redirect happened after your initial choice, this I 
cannot see
of course.


Michael.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread LacaK via fpc-devel 



Dňa 27.9.2021 o 14:03 Michael Van Canneyt napísal(a):



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:






Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to 
do "cherry-pick" ... trying do it - I see there (in step 4: Pick 
into branch) only main branch and not fixes branch. So I do not 
know how to do it ...


In the "pick into branch' dropdown, remove the 'main' from the 
search box and start typing "fixes". The fixes branch will then 
appear.




Yes ;-) this works ... but after I click button "Cherry-pick", I get 
page not found (I am redirecting to some URL which does not exists:


https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-15dfa2e0_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964) 





You must do this operation in the FPC source repository, not in your 
fork.
Yes I do it in 
https://gitlab.com/freepascal.org/fpc/source/-/commit/a8cd770b3cdfcad4a383ac1cca651c315269cc35 



And I get then redirect to: 
https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-a8cd770b_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964 



That's strange because it should again go to the free pascal project. 
What target project did you choose ?


Pick into project = freepascal.org/fpc/source
Pick into branch = fixes_3_2

L.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread Michael Van Canneyt via fpc-devel 



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:






Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to 
do "cherry-pick" ... trying do it - I see there (in step 4: Pick 
into branch) only main branch and not fixes branch. So I do not 
know how to do it ...


In the "pick into branch' dropdown, remove the 'main' from the 
search box and start typing "fixes". The fixes branch will then appear.




Yes ;-) this works ... but after I click button "Cherry-pick", I get 
page not found (I am redirecting to some URL which does not exists:


https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-15dfa2e0_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964) 




You must do this operation in the FPC source repository, not in your 
fork.
Yes I do it in 
https://gitlab.com/freepascal.org/fpc/source/-/commit/a8cd770b3cdfcad4a383ac1cca651c315269cc35


And I get then redirect to: 
https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-a8cd770b_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964


Just noticed:

If you look at the source and target project IDs you see they are different,
that explains why you get these strange results. Make sure the target
project is freepascal.org/fpc/source

Michael.___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread Michael Van Canneyt via fpc-devel 



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:






Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to 
do "cherry-pick" ... trying do it - I see there (in step 4: Pick 
into branch) only main branch and not fixes branch. So I do not 
know how to do it ...


In the "pick into branch' dropdown, remove the 'main' from the 
search box and start typing "fixes". The fixes branch will then appear.




Yes ;-) this works ... but after I click button "Cherry-pick", I get 
page not found (I am redirecting to some URL which does not exists:


https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-15dfa2e0_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964) 




You must do this operation in the FPC source repository, not in your 
fork.
Yes I do it in 
https://gitlab.com/freepascal.org/fpc/source/-/commit/a8cd770b3cdfcad4a383ac1cca651c315269cc35


And I get then redirect to: 
https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-a8cd770b_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964


That's strange because it should again go to the free pascal project. 
What target project did you choose ? Normally that should be the project:


freepascal.org/fpc/source

I did this operation for the commit you indicated, the following is the result:

https://gitlab.com/freepascal.org/fpc/source/-/merge_requests/57

Michael.___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread LacaK via fpc-devel 





Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to 
do "cherry-pick" ... trying do it - I see there (in step 4: Pick 
into branch) only main branch and not fixes branch. So I do not 
know how to do it ...


In the "pick into branch' dropdown, remove the 'main' from the 
search box and start typing "fixes". The fixes branch will then appear.




Yes ;-) this works ... but after I click button "Cherry-pick", I get 
page not found (I am redirecting to some URL which does not exists:
https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-15dfa2e0_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964) 



You must do this operation in the FPC source repository, not in your 
fork.
Yes I do it in 
https://gitlab.com/freepascal.org/fpc/source/-/commit/a8cd770b3cdfcad4a383ac1cca651c315269cc35


And I get then redirect to: 
https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-a8cd770b_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964


With "404 Page Not Found "

When I return back to commit I see there message: "The commit has been 
successfully cherry-picked into cherry-pick-a8cd770b. You can now submit 
a merge request to get this change into the original project."


L.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread Michael Van Canneyt via fpc-devel 



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:




Dňa 27.9.2021 o 9:13 Michael Van Canneyt napísal(a):



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:


Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to do 
"cherry-pick" ... trying do it - I see there (in step 4: Pick into 
branch) only main branch and not fixes branch. So I do not know how to 
do it ...


In the "pick into branch' dropdown, remove the 'main' from the search 
box and start typing "fixes". The fixes branch will then appear.




Yes ;-) this works ... but after I click button "Cherry-pick", I get 
page not found (I am redirecting to some URL which does not exists:

https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-15dfa2e0_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964)


You must do this operation in the FPC source repository, not in your fork.

Michael.___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread LacaK via fpc-devel 



Dňa 27.9.2021 o 9:13 Michael Van Canneyt napísal(a):



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:


Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to do 
"cherry-pick" ... trying do it - I see there (in step 4: Pick into 
branch) only main branch and not fixes branch. So I do not know how to 
do it ...


In the "pick into branch' dropdown, remove the 'main' from the search 
box and start typing "fixes". The fixes branch will then appear.




Yes ;-) this works ... but after I click button "Cherry-pick", I get 
page not found (I am redirecting to some URL which does not exists:

https://gitlab.com/lacak.sk/free-pascal-fpc-source/-/merge_requests/new?merge_request%5Bsource_branch%5D=cherry-pick-15dfa2e0_request%5Bsource_project_id%5D=29308295_request%5Btarget_branch%5D=fixes_3_2_request%5Btarget_project_id%5D=28644964)

May be that in my Fork branch "fixes_3_2" does not exists?

L.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread Michael Van Canneyt via fpc-devel 



On Mon, 27 Sep 2021, LacaK via fpc-devel wrote:


Hello,
commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to do 
"cherry-pick" ... trying do it - I see there (in step 4: Pick into branch) 
only main branch and not fixes branch. So I do not know how to do it ...


In the "pick into branch' dropdown, remove the 'main' from the search box and start typing "fixes". 
The fixes branch will then appear.


Please try and report if this works for you. 
Maybe we need to improve the instructions.


Michael.___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-27 Thread LacaK via fpc-devel 

Hello,

commit d68ce429ab6d94c8ffb251304df6cd7b97e99703
Author: lacak 
Date:   Tue Oct 27 10:01:30 2020 +

commit 15dfa2e0c9ea5071af78d6ddbaf699ae95805630
Author: lacak 
Date:   Tue Oct 27 11:34:22 2020 +

commit a8cd770b3cdfcad4a383ac1cca651c315269cc35
Author: lacak 
Date:   Tue Oct 27 13:11:47 2020 +

commit b5a1c93ec282cedd9aa14c384e913c73ab9c087c
Author: lacak 
Date:   Tue Oct 27 13:16:16 2020 +

commit 54f85eec5676bd47db3d9d5a605f28611c589c0f
Author: lacak 
Date:   Tue Oct 27 13:34:43 2020 +

commit 63aed04024b993641624f6bf6e7e738a0ae80e05
Author: lacak 
Date:   Tue Oct 27 13:58:29 2020 +

commit 63aed04024b993641624f6bf6e7e738a0ae80e05
Author: lacak 
Date:   Tue Oct 27 13:58:29 2020 +

commit 7f6d0fec96cedb1f3e7f8095a6b106f07b61b288
Author: michael 
Date:   Tue Oct 27 14:27:49 2020 +

commit 6c2554af69295f35a5ae71cac937623082025422
Author: lacak 
Date:   Tue Oct 27 14:42:41 2020 +000

commit eb4bc9d153f69392bb5e2b41a121690815c0a3e6
Author: lacak 
Date:   Tue Oct 27 15:01:57 2020 +

commit 7ee3b01effe057752ed5d92d8718e93f48fc44af
Author: lacak 
Date:   Wed Oct 28 12:35:03 2020 +

commit 806ddcdbbcb92cefcb19382cb85a729d738f54ec
Author: lacak 
Date:   Wed Oct 28 12:49:22 2020 +

commit 78e7ea6fbf4930c94bf4aa672184baa1ce8bdbab
Author: lacak 
Date:   Wed Oct 28 14:32:20 2020 +

commit 28d1ad595a784269d56e2e4c34dffdf128e7475d
Author: lacak 
Date:   Wed Oct 28 14:37:36 2020 +

commit 5f04bb4a8e9716103a9346d88fd72b631a6c79f9
Author: lacak 
Date:   Thu Oct 29 05:58:05 2020 +

commit 738959ce59b85e79f068f8a9493ea11f7e4fa1f3
Author: lacak 
Date:   Tue Dec 1 09:31:31 2020 +

commit ab86ce7e62db2add637961e3ff98a7703c86cb2c
Author: lacak 
Date:   Mon Jul 12 12:17:03 2021 +

Sorry for so long list, but I absolutely do not understand how to do 
"cherry-pick" ... trying do it - I see there (in step 4: Pick into 
branch) only main branch and not fixes branch. So I do not know how to 
do it ...


L.

As the dust of the switch to git settles we would like to start 
preparing the next release (3.2.4). To do so, some stuff from main 
(former trunk) might need to be merged as well as regressions against 
3.2.2 need to be fixed. To propose commits to be merged to fixes, 
either propose them here or fill a cherry pick request on gitlab 
(preferred, see 
https://wiki.freepascal.org/FPC_git#Submitting_a_request_to_merge.2Fcherry-pick_a_certain_commit_to_fixes 
).


A log of not yet considered commits can be found at 
https://gitlab.com/freepascal.org/fpc/merging/-/blob/main/eligible.log 



For regressions against 3.2.2, please fill a bug report on gitlab.


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

[fpc-devel] Preparing 3.2.4, call for merge request and regressions

2021-09-26 Thread Florian Klämpfl via fpc-devel 
As the dust of the switch to git settles we would like to start preparing the 
next release (3.2.4). To do so, some stuff from main (former trunk) might need 
to be merged as well as regressions against 3.2.2 need to be fixed. To propose 
commits to be merged to fixes, either propose them here or fill a cherry pick 
request on gitlab (preferred, see 
https://wiki.freepascal.org/FPC_git#Submitting_a_request_to_merge.2Fcherry-pick_a_certain_commit_to_fixes).

A log of not yet considered commits can be found at 
https://gitlab.com/freepascal.org/fpc/merging/-/blob/main/eligible.log 


For regressions against 3.2.2, please fill a bug report on gitlab.

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel