camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: CamelContextLifecycle Has a Glaring Deficiency
Date Sun, 10 Nov 2013 08:27:13 GMT
Yes you can do git pull requests from github as any other github project.
https://github.com/apache/camel/

When doing a pull request
https://github.com/apache/camel/pulls

The only thing we cannot do is to pull and close. And the creator of
the pull request would have to close the pull request manually later.

As the ASF master repo is also git now the sync between the 2 is now
faster, so I don't think there is no longer a day behind.
http://camel.apache.org/source.html



On Sun, Nov 10, 2013 at 6:31 AM, Robert Simmons <kraythe@gmail.com> wrote:
> I was wondering. It still says subversion and I wanted to create a patch on this. With
git a pull request is easy.
>
> Sent from my iPad
>
>> On Nov 9, 2013, at 10:21 AM, Harald Wellmann <hwellmann.de@gmail.com> wrote:
>>
>> Am 09.11.2013 09:10, schrieb Claus Ibsen:
>>> And we love contributions so you are welcome to work on a patch or pull request
>>> http://camel.apache.org/contributing.html
>>
>>
>> Could someone please update the Contributing guidelines? The document still refers
to Subversion and patches.
>>
>> Is the GitHub mirror still one day behind?
>>
>> Is there any advantage in using the Apache Git repo? I see the obvious disadvantage
of having no pull requests as in GitHub.
>>
>> Are there still any restrictions regarding GitHub pull request + JIRA issue?
>>
>> These days, contributing code to a project shouldn't be harder than that. ASF processes
sometimes feel a bit dated... Or maybe it's just the process documentation ;-)
>>
>> Regards,
>> Harald
>>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message