Subject: Re: [boost] Git Modularization hiccups
From: Lars Viklund (zao_at_[hidden])
Date: 2013-05-24 01:10:46
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?
Relying on everyone to mutate their client settings just right doesn't
exactly scale out well, particularly not to end users.
> > * Same problem with bootstrap.sh. IIRC, it is important that the .sh
> > files have the Unix line endings.
> > * c++boost.gif not present in trunk, present in master.
> > * index.html missing in master.
> > * Jamfile.v2 and Jamroot.jam not present in trunk, present in master.
> > * INSTALL missing in master.
> > * LICENSE_1_0.txt has Unix line endings in trunk, Windows line endings
> > in master.
> > * project-config.jam missing in master.
> > * rst.cc missing in master.
> > * README.txt not present in trunk, present in master.
> I'll look into these; thanks.
-- Lars Viklund | zao_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk