On Wed, Nov 22, 2017 at 11:01:22AM +0900, Junio C Hamano wrote:
> Torsten Bögershausen writes:
>
> >> I want to have LF line endings in the repository and CRLF endings in
> >> the working copy. (Because I use windows-exclusive tools to develop.)
> >
> > Side note: If you ever want
Torsten Bögershausen writes:
>> I want to have LF line endings in the repository and CRLF endings in
>> the working copy. (Because I use windows-exclusive tools to develop.)
>
> Side note: If you ever want to push your repository somewhere,
> it would be good practice to have a
On Tue, Nov 21, 2017 at 01:18:30PM +0800, Vladimir Nikishkin wrote:
> Hello, everyone.
>
> I have the following question.
>
> So I have a fresh git repository after git init, on Windows.
>
> core.autocrlf is true explicitly, and core.safecrlf is true implicitly.
>
> I want to have LF line
Vladimir Nikishkin writes:
> I want to have LF line endings in the repository and CRLF endings in
> the working copy. (Because I use windows-exclusive tools to develop.)
>
> But for start I have my code with LF endings, because I got it from a
> fellow developer, who
Vladimir Nikishkin writes:
> So I put the source in the working directory and tell git to make
>
> git diff --stat
>
> and I see the (ambiguous) warnings:
>
> 'warning: LF will be replaced by CRLF in filename.m.
> The file will have its original line endings in you working
Hello, everyone.
I have the following question.
So I have a fresh git repository after git init, on Windows.
core.autocrlf is true explicitly, and core.safecrlf is true implicitly.
I want to have LF line endings in the repository and CRLF endings in
the working copy. (Because I use
6 matches
Mail list logo