my personal history with git tells me that autocrlf=false works better - as it has the lowest surprise element. so I'd vote for setting that, and redoing all files to CRLF (we can have the "shortest script" contest. I bet that BOO would win)
On Fri, Apr 9, 2010 at 10:55 PM, Mauricio Scheffer < [email protected]> wrote: > Krzysztof and I have been running a couple of tests today. > The .gitattributes solution didn't work out. > So these are the solutions I can think of: > > * setting core.autocrlf to true, or > * converting all files with LF (like AbstractHandler.cs) to CRLF so > they're stored as CRLF in the repo > > Does anyone have any other solution? > > Previous thread about this: > > http://groups.google.com/group/castle-project-devel/browse_thread/thread/de27675cd7f08259 > > For reference: spark uses core.autocrlf false, mvccontrib uses true, > and FNH uses false > > Cheers, > Mauricio > > On Mar 30, 4:33 pm, SimoneB <[email protected]> wrote: > > Ouch, sorry, google showed me no replies to this thread until I > > submitted mine. > > > > On Mar 30, 9:32 pm, SimoneB <[email protected]> wrote: > > > > > > > > > Isn't core.autocrlf=true made for this exact reason? > > > > > On Mar 30, 8:09 am, Krzysztof Ko¼mic (2) <[email protected]> wrote: > > > > > > I'm starting a new thread for this, not to pollute the other > > > > discussion. > > > > > > I vote *for* frictionless working with Git. As discussed before I had > > > > issues with files shown as modified just after I did clean clone. I > > > > have this working now, but while fixing one thing, that introduced > > > > another. > > > > In repository we keep files with lf, and I work on Windows. When I > add > > > > a new file it gets added with crlf which leads to us having mixed > > > > lines ending in the repository. > > > > > > Worse, when I start editing lf file, it breaks ReSharper, which can't > > > > handle them. Every refactoring either blows up my VS or ends up with > > > > me having a file with mixed line endings. I then tell VS to convert > > > > line endings to crlf so that I can work with it and with ReSharper, > > > > and then change line endings back manually in Notepad++. > > > > > > Hopefully I don't have to tell you what PITA that is. > > > > > > So I'm for resolving these issues, by whatever means people more > > > > experienced with Git than myself find best. > > > > > > Krzysztof > > > > > > On 30 Mar, 03:26, Mauricio Scheffer <[email protected]> > > > > wrote:> Yes, it can be changed at any time (not for the entire > history of course, > > > > > that would need history rewriting), it's not hard, seehttp:// > help.github.com/dealing-with-lineendings/ > > > > > <http://help.github.com/dealing-with-lineendings/>This was > discussed not > > > > > long ago and several people voted against autocrlf so it remains > that way: > http://www.mail-archive.com/[email protected]/msg... > > > > > > > < > http://www.mail-archive.com/[email protected]/msg...> > > > > > Cheers, > > > > > Mauricio > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.idcc.co.il - הכנס הקהילתי הראשון למפתחי דוטנט - בואו בהמוניכם -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
