On Tue, Feb 10, 2015 at 6:49 AM, Torsten Bögershausen wrote:
> add that to the repo, do the normalization and push.
I did LF normalization over history. Looks like everything worked
correctly, just wondering, what does the WARNING mean?
$ git filter-branch --tree-filter '~/fix-eol.sh' -d /dev/s
On Tue, Feb 10, 2015 at 4:32 PM, Torsten Bögershausen wrote:
> On 2015-02-10 11.52, Piotr Krukowiecki wrote:
>>
>> So far:
>> 1. msysgit can't checkout a one file (saying filename too long, the
>> relative path has 215 bytes) - probably not related to EOL issue.
>> Cygwin git works ok. So I did no
On 2015-02-10 11.52, Piotr Krukowiecki wrote:
> On Tue, Feb 10, 2015 at 6:49 AM, Torsten Bögershausen wrote:
>> Which Git versions are you using ?
>
> The one I'm testing currently:
>
> git version 1.7.9 (cygwin)
> git version 1.9.0.msysgit.0 (msys)
> EGit from Eclipse Luna
>
> Cygwin git is a
On Tue, Feb 10, 2015 at 6:49 AM, Torsten Bögershausen wrote:
> Which Git versions are you using ?
The one I'm testing currently:
git version 1.7.9 (cygwin)
git version 1.9.0.msysgit.0 (msys)
EGit from Eclipse Luna
Cygwin git is a bit old, as I see now. Will try to update later.
> How many peo
On 02/09/2015 11:22 PM, Piotr Krukowiecki wrote:
>Any other suggestions?
My, somewhat personally, suggestion:
If there is more than one developer, don't use core.autocrlf at all-
it is a local setting, which doesn't travel through the repo, and
is slightly different in Git Egit, depending on the
Hi,
in short: how to do svn->git conversion, or how to configure git/EGit
so that Windows/Linux users are happy with EOLs?
Long story:
recently I converted (with git-svn) an svn repository to git. This
created git repository with Windows (CRLF) end of line files. I
suppose the original svn repo
6 matches
Mail list logo
