policy for upstream-sync

[Walter Rabus]

Hi,

I'd like to try mutt and mutt-kz sounds very good to me so far.
I'd like to ask what the policy for mutt-kz is regarding
upstream-development. Will upstream-development be merged into mutt-kz
or is this definitely a separate project now? I saw the recent thread
about upstream-patches merged into mutt-kz, but denoted as
"(cherry-picked)", therefore I'm not sure about the policy in place here.

This is especially interesting for me with regard to
config-compatibility, as I am still in the testing-phase of mutt and
different versions of it and I'm not sure how changing to a different
mutt-[insert_patchset_here] might affect the reusability of the
configuration. Therefore my second question: is mutt-kz fully
config-compatible to mutt except for additional configurations that
result from added patches?

I would be very glad if someone could bring a little light into this.

Thanks a lot,
Walter

[Karel Zak]

On Mon, Mar 02, 2015 at 01:02:15AM +0100, Walter Rabus wrote:
>  I'd like to try mutt and mutt-kz sounds very good to me so far.
>  I'd like to ask what the policy for mutt-kz is regarding
>  upstream-development. Will upstream-development be merged into mutt-kz
>  or is this definitely a separate project now? I saw the recent thread
>  about upstream-patches merged into mutt-kz, but denoted as
>  "(cherry-picked)", therefore I'm not sure about the policy in place here.
Well, we have no any strict policy -- if possible then we use patches
from original mutt. That's all.

>  This is especially interesting for me with regard to
>  config-compatibility, as I am still in the testing-phase of mutt and
>  different versions of it and I'm not sure how changing to a different
>  mutt-[insert_patchset_here] might affect the reusability of the
>  configuration. Therefore my second question: is mutt-kz fully
>  config-compatible to mutt except for additional configurations that
>  result from added patches? 
I don't remember any backwardly incompatible changes, except the new
extension of course. Note that the extensions add many many new things
to config files, so for example config file from mutt-kz with virtual
folders will unreadable for the original mutt.

    Karel

-- 
 Karel Zak  <kzak(a)redhat.com&gt;
 http://karelzak.blogspot.com