From: Felipe Contreras <felipe.contreras@gmail.com>
To: David Bremner <david@tethera.net>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: [PATCH 00/13] vim: a bunch of updates from upstream
Date: Mon, 19 Apr 2021 15:44:41 -0500 [thread overview]
Message-ID: <CAMP44s2w_KSamt8dPNe8Ez+EeBUHM8P3t-=GvyLRkwwZB24=hg@mail.gmail.com> (raw)
In-Reply-To: <87h7k260kr.fsf@tethera.net>
On Mon, Apr 19, 2021 at 5:16 AM David Bremner <david@tethera.net> wrote:
>
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
> > I finally took some time to update notmuch-vim and include some fixes,
> > as well as pull requests.
> >
> > Here are the transplanted patches.
> >
>
> So, big picture question. If notmuch is not upstream for this code,
> should we be distributing it?
I'm not sure which should be considered "upstream" at this point.
Apparently there's also a fork by Ian Main that a lot of people are
using.
From my point of view the code in notmuch is the one that has been
maintained the best. It also has the advantage that there's debian
packaging.
However, it doesn't have all the improvements of my code-base, nor the
features from Ian's code-base.
If I manage to:
1. Provide debian packaging
2. Merge the important features from Ian's code (cleanly)
3. Remain active merging future patches
Then I think we could consider removing the vim stuff from notmuch. In
the meantime I think the three code-bases serve a purpose.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-04-19 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 22:48 [PATCH 00/13] vim: a bunch of updates from upstream Felipe Contreras
2021-04-18 22:48 ` [PATCH 01/13] vim: fix Mail 2.8.0 warning Felipe Contreras
2021-04-26 23:10 ` David Bremner
2021-04-18 22:48 ` [PATCH 02/13] vim: doc: small fixes Felipe Contreras
2021-04-18 22:48 ` [PATCH 03/13] vim: doc: minor spelling fix Felipe Contreras
2021-04-18 22:48 ` [PATCH 04/13] vim: fix for missing parts Felipe Contreras
2021-04-18 22:48 ` [PATCH 05/13] vim: show first part if no text part is detected Felipe Contreras
2021-04-18 22:48 ` [PATCH 06/13] vim: trivial cleanup Felipe Contreras
2021-04-18 22:48 ` [PATCH 07/13] vim: use notmuch config command Felipe Contreras
2021-04-18 22:48 ` [PATCH 08/13] vim: trivial cleanup Felipe Contreras
2021-04-18 22:48 ` [PATCH 09/13] vim: option to add email address to reply quote Felipe Contreras
2021-04-18 22:48 ` [PATCH 10/13] vim: option to add reply quote datetime Felipe Contreras
2021-04-18 22:48 ` [PATCH 11/13] vim: syntax: fix message description highlighting Felipe Contreras
2021-04-18 22:48 ` [PATCH 12/13] vim: remove backwards compatibility wrappers Felipe Contreras
2021-04-18 22:48 ` [PATCH 13/13] vim: README: sync with upstream Felipe Contreras
2021-04-19 10:16 ` [PATCH 00/13] vim: a bunch of updates from upstream David Bremner
2021-04-19 20:44 ` Felipe Contreras [this message]
2021-04-19 22:14 ` David Bremner
2021-04-20 3:21 ` Felipe Contreras
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMP44s2w_KSamt8dPNe8Ez+EeBUHM8P3t-=GvyLRkwwZB24=hg@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).