2013. Can them produced because of previous broken
commits? And probably you can be right about java git wrappers can
produce this issues, I'll try to make a broken repo from scratch
later.
Ivan
2013/4/17 Ivan Lyapunov :
> I ment the same because git changes the version too. Also
> netbe
, Apr 17, 2013 at 09:22:01AM +0400, Ivan Lyapunov wrote:
>> I checked René Scharfe's patch and it works - no more git log crash.
>> Also I checked a broken commits by git show and the most of them
>> created by me. I can confirm I never used anyting else except console
>>
e way to fix this
errors in repo, since we found the same bugs in our Eclipse-based
Android project repo
Ivan
2013/4/17 Ivan Lyapunov :
> Looks like I missed a lot of fun I'm sleeping ;)
>
> The current repo is a product of our core crossplatform team, working
> on Linux/MacOSX/
gt;> the next caller, provide a string consisting of the number zero as
>> default value, representing the UNIX epoch. That's the value that
>> git log showed before it was converted to use split_ident_line().
>>
>> Reported-by: Ivan Lyapunov
>> Signed-off
4 matches
Mail list logo