public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New package neomutt
Date: Mon, 31 Jul 2017 12:52:51 +0200	[thread overview]
Message-ID: <20170731105251.GG1848@gentoo.org> (raw)
In-Reply-To: <20170731095558.GD820@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

On 31-07-2017 04:55:58 -0500, Matthew Thode wrote:
> On 17-07-31 09:11:19, Nicolas Bock wrote:
> > Hi,
> > 
> > I would like to add neomutt to the tree. This new package is meant 
> > as an alternative and not a replacement of the existing mutt 
> > package.
> > 
> > Thanks,
> > 
> > Nick
> > 
> > -- 
> > Nicolas Bock <nicolasbock@gentoo.org>
> 
> It was my understanding that neomutt was mainly mutt with a bunch of
> patches added on, from what I can see, those patches are already handled
> by use flags in the mutt package itself.
>
> https://www.neomutt.org/about.html describes itself as a large set of
> feature patches and not a fork as well.  Are there missing patches that
> need to be added to the mutt package?

These days NeoMutt really is a fork, with a complete code-re-indent,
function name changes, etc.[1]  They move fast, deviating from Mutt and
no longer submit patches to Mutt.  It remains to be seen where both
projects end up, IMO.  It is no longer feasible to add features from
NeoMutt to Mutt, and Mutt moves along its own path (with
features/improvements) as well.

For now it seems useful to me to have both mutt and neomutt around.  I
sent my detailed comments on the neomutt ebuild to Nicholas off-list
already.  The changes suggested should show even more how the two are
different.

Thanks,
Fabian

[1] http://mailman.neomutt.org/pipermail/neomutt-devel-neomutt.org/2017-April/000364.html

-- 
Fabian Groffen
Gentoo on a different level

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-07-31 10:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  7:11 [gentoo-dev] New package neomutt Nicolas Bock
2017-07-31  7:23 ` Nicolas Bock
2017-07-31  8:34   ` Patrice Clement
2017-08-10  4:37     ` Nicolas Bock
2017-07-31 12:15   ` Floyd Anderson
2017-08-10  4:34     ` Nicolas Bock
2017-07-31  7:44 ` Michał Górny
2017-07-31  7:59   ` Nicolas Bock
2017-07-31  9:55 ` Matthew Thode
2017-07-31 10:52   ` Fabian Groffen [this message]
2017-08-05 20:13     ` Matthew Marchese
2017-08-10  4:58 ` Nicolas Bock
2017-08-10  7:40   ` Michał Górny
2017-08-10  7:54     ` Fabian Groffen
2017-08-10  8:10       ` Michał Górny
2017-08-10  9:35         ` Nicolas Bock
2017-08-10 12:13           ` Marc Schiffbauer
2017-08-10 12:16             ` Fabian Groffen
2017-08-10 14:09               ` Michał Górny
2017-08-10 14:32                 ` Fabian Groffen
2017-08-10 13:59           ` Michał Górny
2017-08-17  5:07         ` Daniel Campbell
2017-08-17  7:48           ` Michał Górny
2017-08-18  1:01             ` Daniel Campbell
2017-09-18 12:02     ` Nicolas Bock
2017-08-10 18:25   ` William Hubbs
2017-09-18 12:08 ` Nicolas Bock
2017-10-03 12:36   ` Nicolas Bock
2017-10-03 20:09     ` Marty E. Plummer
2017-10-03 20:33       ` Nicolas Bock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170731105251.GG1848@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox