Also another benefit of doing this via a PR is that you will have commits
listed here https://github.com/apache/camel/graphs/contributors :-)
On Mon, Dec 21, 2015 at 1:59 PM, Jon Anstey wrote:
> Hey guys,
>
> If everything is ready, a PR based off master [1] would be nicer for the
> reviewer rat
Hey guys,
If everything is ready, a PR based off master [1] would be nicer for the
reviewer rather than copying in code manually from hqstevenson/camel-mllp.
We mention GitHub PRs here https://camel.apache.org/contributing.html
Thanks!
Jon
[1] https://github.com/apache/camel/tree/master
On Mon,
Oops, wrong Jira:
https://issues.apache.org/jira/browse/CAMEL-9416
On Mon, Dec 21, 2015 at 12:39 PM, Jamie G. wrote:
> Hi All,
>
> We've opened Camel-5296 Adding camel-mlll component to Apache Camel's Jira:
>
> https://issues.apache.org/jira/browse/CAMEL-5296
>
> Quinn and I believe we have the c
Hi All,
We've opened Camel-5296 Adding camel-mlll component to Apache Camel's Jira:
https://issues.apache.org/jira/browse/CAMEL-5296
Quinn and I believe we have the code to the point that's it time to
have the community review and upon acceptance merge into the Camel
2.17.x (master) branch.
Ple
