Well, since the thread was revived anyway... Ludovic Courtès <l...@gnu.org> writes:
> Hi again! > > Over the years, consensus emerged that ‘core-updates’, as a branch where > we lump together all sorts of rebuild-the-world changes, is no longer > sustainable. So, uh, how should I sent patches for that? Before, I was able to mark patches as intended for core-updates. But since that branch is no more, what should I do? Where should we, non-committers, who do not have a dedicated "focused" branch, send patches that cause a lot of rebuilds? I tried to find answer in the manual (section 22.10) but did not notice anything relevant. Have a nice day, Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
