Re: [boost] [git help] Cloning the boost git repository recursively seems to have issues.

Subject: Re: [boost] [git help] Cloning the boost git repository recursively seems to have issues.
From: Ahmed Charles (acharles_at_[hidden])
Date: 2013-11-01 15:04:53

From: s_sourceforge_at_[hidden]
To: boost_at_[hidden]
Date: Fri, 1 Nov 2013 13:05:56 -0400
Subject: Re: [boost] [git help] Cloning the boost git repository recursively	seems to have issues.

On 1 Nov 2013 at 0:37, Ahmed Charles wrote:
 
> Is there a local change that I can make that would make the situation better?
 
Yes.
 
# Remove everything from the index.
git rm --cached -r .
 
# Write both the index and working directory from git's database.
git reset --hard
 
# Prepare to make a commit by staging all the files that will get 
normalized.
# This is your chance to inspect which files were never normalized. 
You should
# get lots of messages like: "warning: CRLF will be replaced by LF in 
file."
git add .
 
# Commit
git commit -m "Normalize line endings"
 
 
The painful part is you'll need to execute this for every git 
submodule :(
 
I was hoping for one that didn't involve a commit, since when Boost2Git runs, all the commits change and I can't cherry-pick the fix on top of a working directory that contains dirty files that will also change with the cherry-pick.
 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost