| 2 Oct 2025 |
 Fernando Rodrigues | Would it be possible to cherry-pick the original commits instead of making new ones? | 22:23:01 |
 jficz | In reply to @sigmasquadron:matrix.org
Would it be possible to cherry-pick the original commits instead of making new ones? That's what the bot tried to do but failed because of conflicts. I don't think it's possible to do it cleanly. | 22:35:24 |
| Fernando Rodrigues | You should still cherry-pick manually and edit the cherry-picks. | 22:45:07 |
| 3 Oct 2025 |
| jficz | ok, I'll try again but I did exactly that I believe (as suggested here, except yes, I somehow managed to base it against master so I rebased against release after that) | 20:57:29 |
| jficz | * ok, I'll try again but I did exactly that I believe (as suggested here, except yes, I somehow managed to base it against master at first so I rebased against release after that) | 20:58:43 |
|  moleksiak joined the room. | 23:30:58 |
| 4 Oct 2025 |
 dish [Fox/It/She] | Something to consider for now/future releases: Something a la the "Release Blockers" thread, but for things that are intended to be cleaned up post-branchoff. I've found a lot of stuff that was intended to be removed in 25.05 or 25.11, but hasn't been yet, so having a central place to track those sorts of things, so that there's a single checklist of items would be good. Obviously, maintainers of packages would be the ones adding things to it, but it's something to think about for the future, maybe? | 02:28:45 |
