On Sat, 12 Apr 2014, David Bremner <da...@tethera.net> wrote:
> dm-list-email-notm...@scs.stanford.edu writes:
>
>>
>> As far as updating the test suite, etc., it's almost certain that the
>> core notmuch developers would be unsatisfied with whatever I've done,
>> since the code base is very clean and has a very uniform style.  So when
>> I say I'd want some "indication that such a change could be upstreamed,"
>> I mean more specifically that someone would be willing to shepherd the
>> process of getting the code into shape.
>>
>
> I think it depends on your definition of shepherd. If it means review
> your patches and tell you what needs to be done, then we can probably
> handle that. Things tend to stall if the patch proposer loses interest
> after the first review, so we're pretty far from "fire and forget".
>
> I'd like to hear one or two more opinions from regular contributors
> before I say "yes, this is something we want to do."

FYI everyone, message modification times has been proposed before [1].

BR,
Jani.


[1] id:1323796305-28789-1-git-send-email-schno...@schnouki.net
http://mid.gmane.org/1323796305-28789-1-git-send-email-schno...@schnouki.net
_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Reply via email to