On Thu, Jun 28, 2012 at 7:20 PM, Justin Deoliveira <jdeol...@opengeo.org>wrote:
> Hey guys,
>
> I put together a first draft of a doc targeted at geotools committers.
>
>
> https://github.com/jdeolive/geotools/blob/gitdoc/docs/developer/procedures/git.rst
>
> Highlights of the doc:
>
> * Describes how we structure and manage our repositories, canonical,
> developer forks, etc...
> * Provides a list of important do's and dont's
> * Provides other recommendations and good practices
> * Provides a basic primer that goes over some of the simple workflows
>
> All of this I just threw together from my experience on other git
> projects, i am certainly open to changing anything that is there.
>
Read it, looks good but I do have questions about pushing.
Say I work off my fork, and then push to canonical... I guess I will have
to push to
my fork as well?
That is, how is one's fork kept in synch with the canonical one, I guess
it's not
something automatic?
Sorry for the silly question, mostly used to work on git against the
canonical only,
and with svn basically doing the same (minus a lot of local branches)
Cheers
Andrea
--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
