<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>Am 22.04.2026 um 20:01 schrieb Warren Postma via fpc-pascal <fpc-pascal@lists.freepascal.org>:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div><div>>As they should. It's then up to the FPC team to backport (cherry-pick) them to a fixes branch.<span class="gmail-im"></span></div><br></div><div>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?</div></div></div></blockquote><div><br></div>No. But managing a branch for every change would basically mean thousands of branches. This is possible for projects like linux or whatever when there are people doing nothing else than managing branches. FPC does not have such resources. Despite this, I think also LLVM despite having huge support uses a cherry pick based approach to port fixes to stable branches.<br><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div><br></div><div>W</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Apr 21, 2026 at 11:04 PM Graeme Geldenhuys via fpc-pascal <<a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tuesday, 21 April 2026 00:16:46 BST Warren Postma via fpc-pascal wrote:<br>
> The currently open PRs seem to 100% target main, not 3_2_4 and<br>
<br>
As they should. It's then up to the FPC team to backport (cherry-pick) them to <br>
a fixes branch.<br>
<br>
> few seem to be cleanly even able to land on main anymore after the many<br>
> months of them sitting open, that's the trick, I think.<br>
<br>
Correct. I'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>
Graeme<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org" target="_blank">fpc-pascal@lists.freepascal.org</a><br>
<a href="https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal" rel="noreferrer" target="_blank">https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal</a><br>
</blockquote></div>
_______________________________________________<br>fpc-pascal maillist - fpc-pascal@lists.freepascal.org<br>https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal<br></div></blockquote></div><br></body></html>