Hello, Am Mon, Jan 23, 2023 at 10:24:56AM +0100 schrieb Simon Tournier: > > Am Wed, Jan 18, 2023 at 04:54:58PM +0000 schrieb Kaelyn: > >> On a side note, I'd recently discovered the flag to pass. To have a > >>subject prefix like "[PATCH core-updates]" (as mentioned in the manual > >>for staging and core-updates patches) instead of the default "[PATCH]", > >>one can pass "--subject-prefix="PATCH core-updates" to git > >>format-patch. > > This sounds like it could be a useful addition to the QA process. > To my knowledge, it is not possible to continuously build core-updates > because the project does not have enough resource (both human power and > machine power).
ah right, that is unfortunate. > Or do you mean mentioning this option of git-format-patch under point #9 > of «Submitting Patches» [4]? Because this option is already in the > manual under «Sending a Patch Series» section: > > Tip: To add a prefix to the subject of your patch, you may use the > ‘--subject-prefix’ option. The Guix project uses this to specify > that the patch is intended for a branch or repository other than > the ‘master’ branch of > <https://git.savannah.gnu.org/cgit/guix.git>. > > git send-email -1 -a --base=auto \ > --subject-prefix='PATCH core-updates' \ > --to=guix-patc...@gnu.org Okay, I did not notice this; so if this is already implemented, even better! On the other subject, I just updated mpfr and mpc on core-updates, and hope that everything will build (with reason, the changes to these projects are rather conservative in general). Andreas