Re: Bug#825821: ITP: neomutt -- NeoMutt is a place to gather all the patches against Mutt.
- To: Elimar Riesebieter <riesebie@lxtec.de>
- Cc: 825821@bugs.debian.org, Victor Jaquez <vjaquez@igalia.com>, Antonio Radici <antonio@dyne.org>, Richard Russon <rich@flatcap.org>, debian-devel@lists.debian.org
- Subject: Re: Bug#825821: ITP: neomutt -- NeoMutt is a place to gather all the patches against Mutt.
- From: Alberto Garcia <berto@igalia.com>
- Date: Mon, 30 May 2016 17:53:38 +0200
- Message-id: <[🔎] 20160530155338.GA25811@igalia.com>
- Mail-followup-to: Elimar Riesebieter <riesebie@lxtec.de>, 825821@bugs.debian.org, Victor Jaquez <vjaquez@igalia.com>, Antonio Radici <antonio@dyne.org>, Richard Russon <rich@flatcap.org>, debian-devel@lists.debian.org
- In-reply-to: <20160530141641.GA17628@galadriel.home.lxtec.de>
- References: <[🔎] 146460602072.10057.9085444029042844547.reportbug@galadriel.home.lxtec.de> <20160530131411.GA8002@igalia.com> <20160530141641.GA17628@galadriel.home.lxtec.de>
(I forgot to Cc debian-devel in my previous e-mail)
> > > NeoMutt is a sophisticated text-based Mail User Agent
> > > supporting MIME, GPG, PGP and threading.
> > > .
> > > NeoMutt was created when Richard Russon (FlatCap) took all
> > > the old Mutt patches, sorted through them, fixed them up and
> > > documented them.
> >
> > Apart from the standard 'mutt' package, there's at least two
> > other packages in Debian with additional patches: 'mutt-kz' and
> > 'mutt-patched'. From the description of this NeoMutt package it
> > looks like it would be a superset of both of them.
> >
> > Is that the case? If so, would you see neomutt replacing mutt-kz
> > and mutt-patched at some point?
>
> I would see that neomutt is a good successor for mutt-patched. As
> far as I understood Richard correct, neomutt includes the notmuch
> feature from mutt-kz and superseded mutt-kz more or less. There will
> be a git branch at neomutt where all Debian specific patches will
> be incoperated and therefor both mutt and neomutt packages will be
> much easier to maintain. Bugs introduced from neomutt's additional
> features can be handled directly, because we don't have to maintain
> a patch. We have to maintain a feature.
Ok, thanks. I don't know the opinion of the mutt-kz and mutt-patched
maintainers but if this one can be the successor of both I guess it
can make sense to have them replaced by neomutt at some point.
I put them in Cc in case they want to say something before neomutt is
packaged.
Regards,
Berto
Reply to: