trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2014

Re: [trinity-devel] Rules for commit patches to r14.0.x branch

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 16 Dec 2014 19:22:40 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> Hi all,
>
> while working on v3.5.13.x was a rule that the patches have always been
> first
> pushed to the master branch and then cherry-picked to v3.5.13-sru branch
> (with necessary modifications). Directly to v3.5.13-sru patches were
> pushed
> very rarely - if they were specific to v3.5.13.x. As an example, the
> current
> patch for setting the target release in tdelibs.
>
> I suppose for r14.0.x branch I will not be alone, who will incorporate
> patches
> into this maintenance branch, so I would like to determine, whether we
> will
> work also on r14.0.x branch under these rules?

I see no reason to change these rules; they ensure that the patches are
incorporated into mainline and tested before application to the backport
branches.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlSQ2uAACgkQLaxZSoRZrGHw1gDfUNYNqMtV0c3tyWLLGT3p+ccH
X/lK5zJedYpzwgDfX9pfRD5wda0pQ6wSyrMET4U9eKWu1O5EdNPHGA==
=t8+n
-----END PGP SIGNATURE-----