Re: revised patch for gmime init, with test.

Subject: Re: revised patch for gmime init, with test.

Date: Fri, 13 Jan 2012 12:52:48 -0800

To: David Bremner, Pieter Praet,


From: Jameson Graef Rollins

On Fri, 13 Jan 2012 05:05:35 -0400, David Bremner <> wrote:
> I thought about this a bit more, and I agree that at least the release
> candidates (basically anything tagged on branch release) ought to be
> merged back to master. Since any series of bugfix patches seems to be
> cause for a new release candidate, this should avoid the need to have
> doubly applied patches.
> I'm less convinced about the need to merge every little doc change and
> debian packaging change back to master right away. This might be a
> purely aesthetic objection; I'm not sure if the extra merge commits
> cause any problems for e.g. bisection.

Doesn't everything need to be merged into master eventually anyway?  It
seems to me that unless it's a change that very narrowly targeting an
issue in a release branch that is not an issue in master, every patch
will ultimately need to be applied to both.  It doesn't really make
sense to me to apply a change to one branch and not the other, if they
will eventually need to be applied to both anyway.

part-000.sig (application/pgp-signature)