Re: Bug with automated processing of git status results

2017-06-30 Thread Torsten Bögershausen 



On 30/06/17 11:09, Matthieu Moy wrote:

Сергей Шестаков  writes:


I understand that we can turn off core.safecrlf, but it's
inconvinient.


Note that you can do that without actually changing the config file:

   git -c core.safecrlf=false status ...


Beside that, I would recommend to set up a .gitattributes file:

$ echo "*.xml text eol=lf" >>.gitattributes
$ git add .gitattributes
$ git commit -m "xml files are text with LF line endings"

Re: Bug with automated processing of git status results

2017-06-30 Thread Matthieu Moy 
Сергей Шестаков  writes:

> I understand that we can turn off core.safecrlf, but it's
> inconvinient.

Note that you can do that without actually changing the config file:

  git -c core.safecrlf=false status ...

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: Bug with automated processing of git status results

2017-06-30 Thread Konstantin Khomoutov 
On Fri, Jun 30, 2017 at 09:00:14AM +0300, Сергей Шестаков wrote:

> I am trying to make an automated processing of "git status" results.
> I execute the command
> 
> git status -z -uno
> 
> I expect that it has stable output format. However, it still can print
> warnings like
> 
> warning: CRLF will be replaced by LF in somefile.xml
> 
> I understand that we can turn off core.safecrlf, but it's
> inconvinient. It would be better if "git status" command had an
> optional parameter that disables any other output besides changed
> files.

The `git status` command supposedly writes their "regular" data to its
standard output while warnings go to its standard error stream.
Is this not the case?

Bug with automated processing of git status results

2017-06-30 Thread Сергей Шестаков 
Hi!

I am trying to make an automated processing of "git status" results.
I execute the command

git status -z -uno

I expect that it has stable output format. However, it still can print
warnings like

warning: CRLF will be replaced by LF in somefile.xml

I understand that we can turn off core.safecrlf, but it's
inconvinient. It would be better if "git status" command had an
optional parameter that disables any other output besides changed
files.

Thanks!
Sergey Shestakov
Playrix