On Sat, Jan 24, 2026 at 06:34:23PM +0800, Kevin J. McCarthy wrote: > On Sat, Jan 24, 2026 at 08:26:06AM +0100, Rene Kita wrote: > > diff --git a/doc/mutt.man b/doc/mutt.man > > index 12f34bd6..1b19b84d 100644 > > --- a/doc/mutt.man > > +++ b/doc/mutt.man > > @@ -306,6 +306,9 @@ for one of the functions listed while Mutt is running. > > .PP > > For a more up-to-date list of bugs, errm, fleas, please visit the > > mutt project's bug tracking system under > > https://gitlab.com/muttmua/mutt/issues. > > +NOTE: The bug tracking system is not meant for feature requests. > > +These should go to the mutt-users mailing list, > > mutt-dev mailing list or mutt-users?
As of now the manual states in 1.2 Mailing Lists: | * <[email protected]> — help, bug reports and feature requests > I understand mutt-dev can seem intimidating, but in the end this is a > discussion by the devs about the feasibility of a feature request. I'm not > sure we want to have that kind of discussion on mutt-users. I agree. Should I move bug reports and feature requests to the dev ML in the manual? > By they way, I'm still planning on releasing 2.3.0 tomorrow. However once > this discussion is finalized we can apply to the stable branch and make sure > they are mentioned in the next appropriate 2.3.x release. If no one vetoes I would add it to the release, it's just docs, we can adjust it easily.
