On 25/05/12 10:17, Jody Garnett wrote: > I think most of our core team is happy with git these days; how about we > schedule the migration after GeoTools 8.0 is released?
+1. At this point I must admit to being somewhat of a git n00b. While I have been using git for local branches, almost all of my remote repositories have been subversion, accessed with git-svn. I have been sheltered therefore by the GeoTools project subversion config from addressing things like git line ending issues. What local settings should GeoTools developers use to ensure correct behaviour on all platforms? Do I need to: $ git config --global core.autocrlf true This might rely on the content of the repository. Sample discussions: http://help.github.com/line-endings/ http://stackoverflow.com/questions/2825428/why-should-i-use-core-autocrlf-true-in-git Do we need to manipulate the subversion repository as it is migrated to git to ensure there are no text files containing CRLF line endings? Are there any other subversion properties whose absence will be missed when we migrate to git? Any other advice from git frequent fliers? (Justin and Gabriel?) Kind regards, -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ 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
