Morning List: I am getting a lot of questions about how uDig uses git today - and I cannot answer all of them from our docs. - http://udig.refractions.net/confluence/display/ADMIN/02+Checkout+Source+Code
The instructions on the above page do not support the "pull request" workflow; can I ask for a volunteer to update the above page to support the pull-request workflow. It may be as simple as linking to the github instructions ... ------------------------------------ I know I end up with: 1) a personal fork of udig-platform (called jive-udig) 2) I have a clone of that on my machine called "origin/master" 3) I have registered udig-platform as "upstream/master" So I end up with: git branch -r origin/HEAD -> origin/master origin/master origin/snapshot upstream/1.1.x upstream/1.2.x upstream/fpagnamenta upstream/master This allows me to do: a) a pull-request from origin/master (i.e. from jive to udig-platform) (yes I am supposed to make a branch so the pull request is clean) b) pull upstream master push (to accept the latest stuff from udig-platform and push it over to my fork) c) accept changes directly on udig-platform; and work directly on udig-platform during release cycle (this is only as I have commit access; something I hope we can sort out for more developers) -- Jody Garnett
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
