On Sat, Jan 24, 2026 at 08:26:06AM +0100, Rene Kita wrote:
As discussed in [0] feature requests should be discussed on the mailing list before being added to the issue tracker. Add some notes to make this more clear to the user.While at it, copy a NOTE from the web site about the need to be subscribed in order to post to a ML. [0]: https://marc.info/?l=mutt-dev&m=176822608723403&w=2 --- Can/Should we also add a note to the issue tracker itself? I can imagine most users go straight to the issue tracker after learning that mutt is hosted on gitlab.
I haven't looked deeply into how to do things like this on gitlab. I agree it would be nice to have at least something on the gitlab issue request tracker if possible.
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?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.
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.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
