On Tue, 2009-06-09 at 13:07 +0200, Øyvind Harboe wrote: > On Tue, Jun 9, 2009 at 1:02 PM, Zach Welch<z...@superlucidity.net> wrote: > > On Tue, 2009-06-09 at 12:54 +0200, Øyvind Harboe wrote: > >> > Some more information about the subject: > >> > > >> > http://www.cygwin.com/ml/cygwin/2008-12/msg00525.html > >> > > >> > I particularly like the postscript. :) We are not alone here. > >> > >> I'm just going to close my eyes and hope I never hear of this > >> again :-) > > > > Not so fast. > > > > Can we reset the configure.in and Makefile.am svn:eol-style properties? > > If these changes did not fix a problem, then I would like to see these > > reverted to prevent future line-ending issues in these files. > > Done. It was a red herring and I've set it back.
Thanks. > >> I've grepped the source tree and "guess-rev.sh" was the .sh > >> file that is used during normal builds that was broken. > > > > I am not sure what that means though. > > If you try to run a .sh file under Cygwin and that file has Windows > line endings, it will fail w/a syntax error. Even with the bash igncr option? > >> Don't know about this one though: > >> > >> ./tools/uncrustify1.sh > > > > Whose file is that? > > Dunno. Based on 'svn log', it looks like Rick's contribution. I am not a fan of automated cleanup tools (other than sed), so I am unlikely to try it. "Machines that can know good style... that'll be the day...."** ;) Cheers, Zach P.S. This is a sentiment that I would love to rue, but I know that the technology is not there yet. If we were, we would not be coding in C. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
