Well redoing work would not be fun / cool :( I have had some luck using Eclipse to sort line endings and more importantly file encodings.
I recently (two months ago) ran into a similar problem with geotools (using git svn). The problem stemmed from allowing git to blindly copying bytes (good!) vs allowing it to process text (bad and scary). If you could identify a file you did not change; we could do a "git checkout" to revert it and then compare to another file and try and see what specifically is different. We can then try a similar step on a couple other files and see if we can get git to notice they are unchanged? ---- For my part I am going to tag uDig now (just got the GeoTools release going) so you can have a bit more of a level playing field (especially good if many files are changed. Jody -- Jody Garnett On Tuesday, 4 October 2011 at 4:33 PM, Severin (aka Cliff) wrote: > Hi all, > > > I have now got a maven+tycho build of udig working with minimal changes to > the current udig master branch. > > I do however now have a problem with git. > > Last night I commited my work on my mac and git decided that I have somehow > changed every single file in the udig project. > > Git now wants to commit a change to every single file back. > > Does anyone know why this has happened and/or how to fix it? > > I'd have to have to go back and re-do all this work as it will require > another two to three days. > > Any help or hints appreciated! > > Cheers, > --Sev > > > -- > "We are dreamers, shapers, singers and makers..." > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
