From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Austin Clements <amdragon@MIT.EDU>, David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Patches for 0.12
Date: Wed, 14 Mar 2012 15:40:11 -0700 [thread overview]
Message-ID: <87fwdahkms.fsf@servo.finestructure.net> (raw)
In-Reply-To: <20120314221601.GN2787@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
On Wed, 14 Mar 2012 18:16:01 -0400, Austin Clements <amdragon@MIT.EDU> wrote:
> > We had a somewhat lively debate about desirablity of the following
> > patch. My decision is that for now, we avoid changing the behaviour of
> > notmuch, and do apply the patch. We can discuss later deprecating or
> > changing this permissive behaviour.
> >
> > id:"1331385931-1610-1-git-send-email-david@tethera.net"
>
> Alternatively, can we just require GMime 2.6.7 by applying
> id:"1331515786-485-1-git-send-email-david@tethera.net"
> instead of
> id:"1331385931-1610-1-git-send-email-david@tethera.net"
> and
> id:"1329852935-3019-1-git-send-email-schnouki@schnouki.net"
> ?
I much prefer this solution (i.e. just require GMime 2.6.7 and no
notmuch patches). I still think we need some sort of coherent approach
for rejecting mbox, but I think it will require a lot more thought.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-03-14 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 14:09 Patches for 0.12 David Bremner
2012-03-14 21:45 ` anecdotical evidence: number mbox files in my maildirs (was: Re: Patches for 0.12) Gregor Zattler
2012-03-14 20:49 ` anecdotical evidence: number mbox files in my maildirs Daniel Kahn Gillmor
2012-03-14 22:16 ` Patches for 0.12 Austin Clements
2012-03-14 22:40 ` Jameson Graef Rollins [this message]
2012-03-15 21:17 ` Austin Clements
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=87fwdahkms.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=amdragon@MIT.EDU \
--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).