On Mon, Aug 10, 2015 at 08:36:35AM +, Benkstein, Frank wrote:
> You are correct that it is also wrong in git v1.7.0. However, it is correct
> in
> v2.4.0.
>
> Another bisect gave me this commit which was included in v2.0.1:
>
> commit 4d4813a52f3722854a54bab046f4abfec13ef6ae
> Author: bri
On 2015-08-10 20.48, Junio C Hamano wrote:
> Torsten Bögershausen writes:
>
>> Actually I could reproduce the following:
>> CRLF in repo, CRLF in working tree, core.autocrlf= true.
>
> What should happen in such a case? Wouldn't autocrlf=true want to
> strip CRLF down to LF? Shouldn't it?
A
Torsten Bögershausen writes:
> Actually I could reproduce the following:
> CRLF in repo, CRLF in working tree, core.autocrlf= true.
What should happen in such a case? Wouldn't autocrlf=true want to
strip CRLF down to LF? Shouldn't it? And if so, "blame" is correct
to say that you are changing
Hello Torsten,
Torsten Bögershausen, Sonntag, 9. August 2015 22:20:
> On 2015-08-08 07.58, Torsten Bögershausen wrote:
>> On 2015-08-07 18.32, Benkstein, Frank wrote:
>>> I am working working on Linux and am examining code in a git repository I do
>>> not know much about. I am only looking at fil
On 2015-08-08 07.58, Torsten Bögershausen wrote:
> On 2015-08-07 18.32, Benkstein, Frank wrote:
>> Hello,
>>
>> I am working working on Linux and am examining code in a git repository I do
>> not know much about. I am only looking at files, not changing anything. On
>> some files in the repositor
On 2015-08-07 18.32, Benkstein, Frank wrote:
> Hello,
>
> I am working working on Linux and am examining code in a git repository I do
> not know much about. I am only looking at files, not changing anything. On
> some files in the repository I get " (Not Committed Yet" for all lines
> w
6 matches
Mail list logo
