Mailing-List: contact dev-help@servicemix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@servicemix.apache.org
Received-SPF: pass (athena.apache.org: domain of janstey@gmail.com designates
 209.85.213.176 as permitted sender)
MIME-Version: 1.0
Date: Thu, 5 Jul 2012 22:42:51 -0230
Message-ID: 
 <CAKxuBd+r0ubV1TYFzbz44SjSbJf+gxaoy=EvZxe=_V+UtFX3fQ@mail.gmail.com>
Subject: [DISCUSS] Set up svnmerge.py on features-4.4.x?
From: Jon Anstey <janstey@gmail.com>
To: dev@servicemix.apache.org
Content-Type: multipart/alternative; boundary=14dae93403698c39d004c41ef6ed

--14dae93403698c39d004c41ef6ed
Content-Type: text/plain; charset=ISO-8859-1

I just had to merge a commit from trunk to features-4.4.x and realized we
didn't have any merge rev tracking in place there. I manually merged the
commit for now but it would be good to have something like we have at Camel
http://camel.apache.org/merging-commits-from-trunk-to-fixes-branch.html for
merging to fixes branches. Anyone mind if I set up a similar process for
the features-4.4.x branch?

Cheers,
Jon

-- 
Cheers,
Jon
---------------
FuseSource
Email: jon@fusesource.com
Web: fusesource.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen

--14dae93403698c39d004c41ef6ed--