Re: [boost] Git Modularization hiccups

Subject: Re: [boost] Git Modularization hiccups
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-05-24 02:00:19

on Thu May 23 2013, Lars Viklund <zao-AT-acc.umu.se> wrote:

> On Thu, May 23, 2013 at 09:37:32PM -0700, Dave Abrahams wrote:
>> 
>> on Thu May 23 2013, Beman Dawes <bdawes-AT-acm.org> wrote:
>> > The remaining hiccups are in the root directory, comparing trunk
>> > to master:
>> >
>
>> > * boost.css is missing content from revisions 36243 and 53553.
>> >
>> > * boost-build.jam has different comments and history. Something is
>> > totally whacky.
>> >
>> > * boostcpp.py contents are the same, but the trunk file has Unix line
>> > endings, the master file has Windows line endings.
>> 
>> Oh well, the way line endings are handled in Git and SVN are divergent.
>> Check your .gitconfig against the output of git --help config;
>> especially core.eol, core.safecrlf, and core.autocrlf
>
> Shouldn't the repositories contain a .gitattributes file indicating the
> eol flavor to be used for text files where it has significance?

Perhaps!  I don't know anything about .gitattributes.  Where can I find
out more?

-- 
Dave Abrahams