James Addison <j...@jp-hosting.net> (2023-06-01): > I haven't used (wasn't aware of!) that before, and don't currently have a > commandline mail client installed, but I'll try that out in future, yep - > thanks. Be prepared to wait a while until I migrate stuff though > (fortunately for everyone here, I'm probably going to be sending much less > communication now that bookworm is nearing done and dusted).
Alright, thanks for considering. I'm very happy you've followed up to a bunch of new and old bug reports, but I must confess that bunch of lines at the top kind of draw the attention away from the actual bts command (if any), and having to carry recipients over from X-Debbugs-Cc to Cc manually is a bit cumbersome, that's why I thought I should ask. I'm definitely *not* asking you to stop working the way you did so far, I was really just wondering whether you considered a different approach. > Sometimes I'm uncertain how much action to take on behalf of a > maintainer, especially without a sense of consensus, and/or without > being familiar with the details; also some packages and bugs feel more > important than others - any of those factors can make me more cautious > (and even then I'm inconsistent, no doubt). I understand the feeling completely! And caution is good! For what it's worth, if you find a bug that's “evidently” closed because a missing feature was implemented, and if you have a version to close the bug report with, please feel free to do so, with -done & Version: pseudo-header. It's easy enough to issue a reopen command if that turned out to be a mistake. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
