|
From: Justin D. <jde...@op...> - 2011-11-11 15:33:27
|
On Fri, Nov 11, 2011 at 8:23 AM, Justin Deoliveira <jde...@op...>wrote: > Well... for now the idea is that no, you wouldn't push changes directly to > this repository. What i had in mind was that one would fork the repo > locally in his/her own account, and mostly work from that. Pushing changes > back into svn will still be down with an svn dcommit from your own copy, > not by pushing back to the canonical github representation. Which actually > brings up a good point I forgot to mention and should write up on the > github wiki page. That is when one clones the github repo it will not be > linked back to svn, that will require another svn init in the clone. > > Process documented here: https://github.com/geotools/geotools/wiki > In terms of keeping the forks up to date... again doing an svn rebase from > your local fork will do that, no need to pull in changes from the github > clone... although i guess one could. > > The main benefit I see is a common history among developers individual > repos, making it easy to share changes and do collaborative branch > development. > > -Justin > > > On Fri, Nov 11, 2011 at 8:08 AM, <chr...@nv...> wrote: > >> Aha, I knew it, it starts get confusing to me. >> >> Does this mean that I can use git for geotools and push my changes to >> this new repo ?. >> >> In which direction is the synchronization between the two repos working. >> >> svn ---> git >> svn <--- git >> svn <---> git (how are conflicts resolved ?) >> >> Cheers >> Christian >> >> >> Zitat von Justin Deoliveira <jde...@op...>: >> >> >> Hi all, >>> >>> I took the liberty of trying to set up a "canonical" github repository. >>> >>> https://github.com/geotools/**geotools<https://github.com/geotools/geotools> >>> >>> The idea is that this would be the repository that developers fork >>> locally >>> to do development like we do today. Having a same base repository makes >>> pushing/pulling changes back and forth quite a bit easier. >>> >>> The repo does not contain the entire history. I created it from about >>> revision 36490, which is shortly before the 2.7.x branch was created. >>> >>> In conjunction, i also set up a couple of new hudson jobs to keep the >>> repo >>> up to date with the latest from svn: >>> >>> http://hudson.opengeo.org/**hudson/view/geotools/job/** >>> geotools-2.7.x-github/<http://hudson.opengeo.org/hudson/view/geotools/job/geotools-2.7.x-github/> >>> http://hudson.opengeo.org/**hudson/view/geotools/job/** >>> geotools-trunk-github/<http://hudson.opengeo.org/hudson/view/geotools/job/geotools-trunk-github/> >>> >>> Let me know what you think and if this is a useful thing to have. >>> >>> -Justin >>> >>> -- >>> Justin Deoliveira >>> OpenGeo - http://opengeo.org >>> Enterprise support for open source geospatial. >>> >>> >> >> >> ------------------------------**------------------------------**---- >> This message was sent using IMP, the Internet Messaging Program. >> >> >> > > > -- > Justin Deoliveira > OpenGeo - http://opengeo.org > Enterprise support for open source geospatial. > > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. |