[fpc-devel] 134 open merge requests - is that normal?

[Marco van de Voort]

Op 7-4-2026 om 15:58 schreef Martin Frb via fpc-devel:
> Actually, I would think the relation between fpc src and build can be 
> described as n to 1
>
> - For any commit in fpc-src there is one fpc build commit that works 
> (others may, but one that should be used)

Not necessarily. The counterexample is that fpcdocs is updated without a 
corresponding fpcsrc commit at all. Typically during release times when 
there is an last minute emergency doc fix.

So while I don't subscribe to your analysis, I do think it is mostly 
about maintaining the link between the various repositories, specially 
for branches that end (RC, release).  So maybe if GIT is incapable, a 
continuous link is too much trouble.

Having a dummy root repo would work around the GIT deficiencies. The 
branches of that repo would double as the "universal" branch moniker, 
and the robo updates for living branches like fixes wouldn't hurt, as 
its history would be pretty much never needed.

> And if you reverse the dependency, that should disappear. You only 
> need the submodule update, when it is technically required.

That is correct, but only for the steady state between releases when 
fpcbuild is mostly dormant. But it doesn't fix the more frantic times 
during release (and then special major-). And it is then, in times of 
relative chaos that the automated links proves its worth.