Re: Preparing FPC 3.2.4 RC2

--===============3169507085952200908==
Content-Type: multipart/alternative; boundary="000000000000e95b8306501052ef"

--000000000000e95b8306501052ef
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>As they should. It's then up to the FPC team to backport (cherry-pick)
them to  a fixes branch.

This feels weird to me for some reason, maybe that's normal in this
project, but it seems more Git-normal to not commit bugfixes straight to
trunk. Is this a holdover from the svn days when that's the only workflow
you had because svn branching was... broken?



W

On Tue, Apr 21, 2026 at 11:04=E2=80=AFPM Graeme Geldenhuys via fpc-pascal <
[email protected]> wrote:

> On Tuesday, 21 April 2026 00:16:46 BST Warren Postma via fpc-pascal wrote=
:
> > The currently open PRs seem to 100% target main, not 3_2_4 and
>
> As they should. It's then up to the FPC team to backport (cherry-pick)
> them to
> a fixes branch.
>
> > few seem to be cleanly even able to land on main anymore after the many
> > months of them sitting open, that's the trick, I think.
>
> Correct. I'll be starting this week, going through all the open MRs and
> triage/label them for the authors to action, so we can get them back up t=
o
> date (or closed).
>
> Regards,
>   Graeme
>
>
>
>
>
> _______________________________________________
> fpc-pascal maillist  -  [email protected]
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>

--000000000000e95b8306501052ef
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>&gt;As they should. It&#39;s then up to the FPC =
team to backport (cherry-pick) them to=C2=A0=C2=A0a fixes branch.<span clas=
s=3D"gmail-im"></span></div><br></div><div>This feels weird to me for some =
reason, maybe that&#39;s normal in this project, but it seems more Git-norm=
al to not commit bugfixes straight to trunk. Is this a holdover from the sv=
n days when that&#39;s the only workflow you had because svn branching was.=
.. broken?</div><div><br></div><div><br></div><div><br></div><div>W</div></=
div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Tue, Apr 21, 2026 at 11:04=E2=80=AFPM Graeme Geldenh=
uys via fpc-pascal &lt;<a href=3D"mailto:[email protected]">f=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">On Tuesday, 21 April 2026 00:16:46 BST Warren=
 Postma via fpc-pascal wrote:<br>
&gt; The currently open PRs seem to 100% target main, not 3_2_4 and<br>
<br>
As they should. It&#39;s then up to the FPC team to backport (cherry-pick) =
them to <br>
a fixes branch.<br>
<br>
&gt; few seem to be cleanly even able to land on main anymore after the man=
y<br>
&gt; months of them sitting open, that&#39;s the trick, I think.<br>
<br>
Correct. I&#39;ll be starting this week, going through all the open MRs and=
 <br>
triage/label them for the authors to action, so we can get them back up to =
<br>
date (or closed).<br>
<br>
Regards,<br>
=C2=A0 Graeme<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
fpc-pascal maillist=C2=A0 -=C2=A0 <a href=3D"mailto:[email protected]=
scal.org" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal=
" rel=3D"noreferrer" target=3D"_blank">https://lists.freepascal.org/cgi-bin=
/mailman/listinfo/fpc-pascal</a><br>
</blockquote></div>

--000000000000e95b8306501052ef--

--===============3169507085952200908==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fpc-pascal maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

--===============3169507085952200908==--