I'm not convinced, that one policy is a good solution, but it really depends on your project. What we do: .bat files with windows line endings .cmd .vbs files with windows line endings .sh files with unix file endings source files (.c .h .py .pl) with unix file endings .txt files with unix file endings The rest untouched: you might add a precommti hook to verify this. SO war we din't bother to automate it, but I must admint, that we had occasional rare jickups. bye N mat wrote: > Hi > > I have two git projects: > -one (A) with linux people only > -one (B) with someone using windows > > As we had "end of line" problems with the person using windows (B), I used: > > git config --global core.autocrlf true > > Following advices from: > http://help.github.com/dealing-with-lineendings/ > > So everything now if fine with project B, but now some problems using > project (A): I wanted to copy the whole project file to another dir, and > now it is complaining about the change, signaling warning: > > CRLF will be replaced by LF in .../A. > > So I don't know exactly what I should do...Should I change all the CRLF > from project A, but people will have also problems, or can I switch the > config, once I'm using project A and B? It is not so clear in my mind > and I would appreciate any advice!! > > Thanks a lot > > Matthieu Stigler > > > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html