On 06/01/20 08:32 AM, Bastien wrote: > Hi Eric, > > Eric Abrahamsen writes: > >> I think in the original discussion the patch went back and forth between >> completing on `package-alist' and completing on `features'. The former >> didn't offer enough, the latter offered too much. > > While not offering "enough", the former is already an improvement, I'd > be in favor of implementing it. The latter really offers too much IMO. Yes, I've come to the same conclusion over time. >> If we complete on `features', that's definitely an issue. I think my >> solution in that version of the patch simply dropped the issue if the >> Maintainer header was emacs-devel, or there was no Maintainer. > > Yes, it looks fine to me like this. > >> My pleasure -- as Dmitry notes, this might not solve the problem that >> this thread is about, but I think it's definitely worthwhile on its own. > > Definitely. What is still needed here so that you can make this change? Here's a new version of the patch. It: 1. doesn't require a package 2. only honors the Maintainer header (not the Author header, if there's no Maintainer) 3. screens out "emacs.devel@gnu.org" as a Maintainer value (we could easily add more values to screen out) 4. uses X-Debbugs-CC instead of Cc 5. Adds a "Package:" pseudo-header Remaining questions: 1. I've seen some reference to a X-Debbugs-Package header, is that honored? 2. Glenn mentioned the fact that some package maintainers might not want anything to do with debbugs. I'm not sure how to handle that situation, except manually. I suppose, if we do end up adding a package maintainer, we could also add a line of text in the intangible instructions saying, "If you don't want to deal with this bug on the Emacs bug tracker, please send a message to XXX-done@debbugs.gnu.org to close it." 3. Lastly, this is a fairly in-your-face change to how Emacs bugs are reported, and I'm not sure everyone agrees it's a good idea! Adding an extra prompt to the process is a bit intrusive. Eric