Shows what I know. Thanks, I'll make sure my repo's up to date. On Wed, Aug 31, 2011 at 10:41 AM, Patrick Earl <[email protected]> wrote:
> The NHibernate repo has all the CRLFs from the SVN conversion. It's > been serving the project well, so I figured I'd leave it in a familiar > state. In a recent commit, I disabled auto-conversion. Make sure you > have the commit that added .gitattributes. You may also have to reset > your index to ensure the changes take effect properly. > > Patrick Earl > > On Wed, Aug 31, 2011 at 2:29 AM, David Schmitt <[email protected]> wrote: > > On 30.08.2011 23:22, [email protected] wrote: > >> > >> What's the correct configuration for making sure line endings come out > >> right? I forked the repo and made some changes, and I found that VS > >> had turned all the line endings in the .csproj files to CRLF and > >> created a bogus diff. > >> > >> I set git config core.autocrlf false, which I thought was supposed to > >> strip out the CRLF in the diffs, but it doesn't seem to make a > >> difference. > > > > To the contrary. autocrlf=false tells git to keep the files exactly as > they > > are. This may lead to spurious changes when windows tools rewrite those > > files. I normally use bot autocrlf and safecrlf set to true. This should > > ensure that files in the repo always are LF-only and that mixed-CRLF/LF > > files need manual fixing before committing. > > > > But this is only general advice, I do not know how the NHibernate repo is > > configured. > > > > Best Regards, David > > >
