https://github.com/neomutt/community
⚠️ Birds-eye view of the Mutt Community
https://github.com/neomutt/community
forks mutt obsolete patches
Last synced: 4 months ago
JSON representation
⚠️ Birds-eye view of the Mutt Community
- Host: GitHub
- URL: https://github.com/neomutt/community
- Owner: neomutt
- Created: 2015-12-27T13:27:31.000Z (over 10 years ago)
- Default Branch: main
- Last Pushed: 2022-06-12T19:07:01.000Z (about 4 years ago)
- Last Synced: 2025-12-26T20:57:30.932Z (6 months ago)
- Topics: forks, mutt, obsolete, patches
- Homepage:
- Size: 29.3 KB
- Stars: 4
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Mutt Community
## What is it?
A list of every fork and patch for mutt.
I searched through https://github.com/ and https://bitbucket.org/ for anything
called "mutt". There were over 700 matches. Many repositories were nothing
to do with mutt and many more were just people's mutt config files.
The remainder, I examined to determine if there was any unique code that I
should consider.
## Why?
To reduce the amount of wasted time and effort for mutt developers.
Mutt development is very conservative and consequently very slow.
This has driven a **lot** of people to fork mutt and roll their own versions.
The mutt community needs rallying around a single point and I'd like this
github team to be that point.
## What's Obsolete?
Many mutt patches don't have an official author/owner/maintainer. They float
around the net in multiple forms. Each patch applied to our development repo
will also reference a list of other patches that it obsoletes. These obsolete
patches will be monitored to ensure any new development isn't missed.
This will simplify the job of future developers.
## Who?
* Rich Russon (FlatCap) <rich@flatcap.org>
* https://flatcap.org/
