On Tue, 17 Jun 2025 13:42:18 -0700, Soren Stoutner <so...@debian.org> wrote: >Regarding working with patch submissions, I greatly prefer an MR. I almost >never merge a request without requesting changes, or at least clarification. >Having the ability to highlight specific lines of code and start a thread >discussing them, and having several threads going at once for different parts >of the code, each of which can independently be marked as completed, is a >workflow that I would find difficult to replicate in email.
Then you surely can point me to documentation about how I, as the MR submitter am supposed to improve the MR. I am not sure whether just pushing my fixed code to the branch that I submitted an MR for will automatically update the MR o whether I am supposed to do some magic chants to have those changes show up in the MR, or whether I am supposed to comment on the thread after pushing an improvement and who is supposed to close the discussion thread in the MR. I guess that a lot of this depends on convention, but in a forge as large as salsa we should have our conventions in writing so that newbies¹ know what to do. Greetings Marc ¹ I have been a DD for two decades, but handling MRs in Salsa is - from both sides of the story - still byzantine to me -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
