> I finally resorted to the Git command line today. With some help from this
> page:
> http://docs.geotools.org/latest/developer/procedures/git.html
>
> and from this page:
> http://learn.github.com/p/normal.html
If I can kindly recommend: http://ndpsoftware.com/git-cheatsheet.html
(Personally I use a client called Tower for most day to day git wrangling).
> I took some brief notes I will try to share on one of my blogs. Perhaps we
> can add this to the GeoTools wiki if others think it will be helpful.
It may be good just to add it to the docs. The user guide has
http://docs.geotools.org/latest/userguide/build/git.html
> I'm really nervous about pushing anything to the GeoTools master using Git.
> I'd like to just work in my fork on GitHub for a while, until I get more
> comfortable using Git from the command line. Would it be a problem if I
> pushed a single batch of changes to the JTIN Version 2 unsupported module in
> the GeoTools master repository in a couple of weeks?
That should be fine, if you are really concerned arrange an IRC time so someone
else with commit access is on hand to try out your change (and recover if
things go bad).
> For the time being, Julian and I will keep working on the code in my SVN repo:
> https://subversion.assembla.com/svn/surveyos/trunk/java/sandbox/jtin_v2/src/
Well the sooner you move to git the easier it will be, consider using "git svn"
for interacting with your above subversion repository.
Cheers,
Jody
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
