Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-14 Thread Antonio Valentino
Hi Even, Il giorno 14/ott/2012, alle ore 01:02, Even Rouault even.roua...@mines-paris.org ha scritto: Just a quick follow-up. I've just received the first pull request ( https://github.com/OSGeo/gdal/pull/1 ) and managed to merge it and commit it to SVN with the following (based on your

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-14 Thread Even Rouault
Hi Antonio, I suppose that at this point you already used git remote add NAME URL git fetch NAME In the context I described, would be NAME = nas-fixes and URL = https://github.com/jef-n/gdal ? Well, I don't remember having used that. Apparently just git pull https://github.com/jef-n/gdal

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-14 Thread Antonio Valentino
Hi Even, Il 14/10/2012 11:54, Even Rouault ha scritto: Hi Antonio, I suppose that at this point you already used git remote add NAME URL git fetch NAME In the context I described, would be NAME = nas-fixes and URL = https://github.com/jef-n/gdal ? yes Well, I don't remember having

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-14 Thread Etienne Tourigny
Hi On Sun, Oct 14, 2012 at 7:49 AM, Antonio Valentino antonio.valent...@tiscali.it wrote: Hi Even, Il 14/10/2012 11:54, Even Rouault ha scritto: Hi Antonio, I suppose that at this point you already used git remote add NAME URL git fetch NAME In the context I described, would be NAME

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-13 Thread Mateusz Loskot
On 14 October 2012 00:02, Even Rouault even.roua...@mines-paris.org wrote: The only annoying (but logical) thing is that I appear as the committer of the changes, instead of the original author. Perhaps there would be an automated way of adding the original git commiter name in the SVN commit

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-11 Thread Ari Jolma
On 10/10/2012 10:49 PM, Etienne Tourigny wrote: Hi Even, On Wed, Oct 10, 2012 at 4:24 PM, Even Rouault even.roua...@mines-paris.org wrote: My feeling is that the main barrier to contribution lies more in understanding how the source works rather than the tools around. Anyway, whatever the

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-11 Thread Etienne Tourigny
Hi On Wed, Oct 10, 2012 at 5:55 PM, Even Rouault even.roua...@mines-paris.org wrote: Le mercredi 10 octobre 2012 21:49:49, Etienne Tourigny a écrit : Hi Even, the main advantage of github is that you can manage patches/pull requests more easily, and it's easy for someone to setup a fork with

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Angelos Tzotsos
On 10/10/2012 02:16 AM, Even Rouault wrote: Le dimanche 07 octobre 2012 11:42:30, Even Rouault a écrit : Hi, Following a recent similar move from MapServer, I've setup an instance of Travis CI, hosted continuous integration service. After each SVN commit in trunk, GDAL is built and the Java,

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Etienne Tourigny
IMHO git (with github) is a great platform for collaboration. You might find yourself swamped with pull requests though... cheers Etienne On Wed, Oct 10, 2012 at 5:34 AM, Angelos Tzotsos gcpp.kal...@gmail.com wrote: On 10/10/2012 02:16 AM, Even Rouault wrote: Le dimanche 07 octobre 2012

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Even Rouault
Le mercredi 10 octobre 2012 15:48:48, Etienne Tourigny a écrit : IMHO git (with github) is a great platform for collaboration. You might find yourself swamped with pull requests though... I'd be curious to know if the current use of SVN really deters people from contributing to GDAL, whereas

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Etienne Tourigny
Hi Even, the main advantage of github is that you can manage patches/pull requests more easily, and it's easy for someone to setup a fork with substantial changes, and anyone can pull that fork and try it without much hassle. The other way of doing it with trac/svn is to upload patches to

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Mateusz Loskot
On 10 October 2012 20:49, Etienne Tourigny etourigny@gmail.com wrote: Hi Even, the main advantage of github is that (...) Guys, you're discuss apples (Even on Git) and oranges (Etienne on GitHub). Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Etienne Tourigny
On Wed, Oct 10, 2012 at 4:52 PM, Mateusz Loskot mate...@loskot.net wrote: On 10 October 2012 20:49, Etienne Tourigny etourigny@gmail.com wrote: Hi Even, the main advantage of github is that (...) Guys, you're discuss apples (Even on Git) and oranges (Etienne on GitHub). sort of - I'm

Re: [gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-10 Thread Even Rouault
Le mercredi 10 octobre 2012 21:49:49, Etienne Tourigny a écrit : Hi Even, the main advantage of github is that you can manage patches/pull requests more easily, and it's easy for someone to setup a fork with substantial changes, and anyone can pull that fork and try it without much hassle.

[gdal-dev] [update] Re: Travis CI continuous integration service for GDAL

2012-10-09 Thread Even Rouault
Le dimanche 07 octobre 2012 11:42:30, Even Rouault a écrit : Hi, Following a recent similar move from MapServer, I've setup an instance of Travis CI, hosted continuous integration service. After each SVN commit in trunk, GDAL is built and the Java, Perl and Python tests are run. Travis CI