It could be more handy if you can create a patch and attached it to the JIRA. It is easy for us to maintain the code and issue tracker.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wednesday, February 6, 2013 at 5:40 AM, Christian Müller wrote: > Hi Jan! > > The official SCM for Apache Camel is SVN. > Most/Many of the committers (including me) are using git-svn as described > at [1]. So Git pull request will work for them. > I think a pointer to the Git repos is fine. But make it clear, it's a read > only mirror from SVN. > > Have in mind: > Git pull request may not work for committers which are only unsing SVN. > I think GitHub has good documentation about working with Git at GitHub. I > think a pointer is sufficient. > > [1] http://wiki.apache.org/general/GitAtApache > > Best, > Christian > > On Tue, Feb 5, 2013 at 9:22 PM, Jan Matèrne (jhm) <apa...@materne.de > (mailto:apa...@materne.de)> wrote: > > > On http://camel.apache.org/source.html is nothing said about sources in > > Git. > > > > Should I add a pointer to http://git.apache.org/, > > git://git.apache.org/camel.git and https://github.com/apache/camel? > > > > > > > > Maybe some notes about how to work at Github (fork, branch, modify, Jira, > > pull request, after Jira closing the pull request) > > > > > > > > Jan > > > --
