Oh and yes I am a +1 on switching over to git. Things i think we want/need
before a full switch.
* a quick primer for people with sample commands for common tasks
* a list of git does and donts, ie don't rebase on a public branch, etc...
* line endings figured out re Bens comment
* a way to get gi
Funny you bring this up Ben. We use git for some internal projects and have
developers on windows that recently ran into this issue and it was a real
pita. Although it was fine up until a developer has to actually be able to
commit just one file with crlf endings, a windows .cmd file that seemed to
On 25 May 2012 13:56, Ben Caradoc-Davies wrote:
> Are there any other subversion properties whose absence will be missed
> when we migrate to git?
>
We lose the svn source and URL keywords. The source keyword is used by
the GeoTools javadoc plugin to add the module information at the top
of the j
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 o
