git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug with automated processing of git status results

From
KKKonstantin Khomoutov <kostix+git@007spb.ru>
Date
Jun 30, 2017, 07:12 UTC
Message-ID
<20170630071219.m757vvyccrp3afli@tigra>
In-Reply-To
<CAM1TZMGXiDpzt3uhpDaE41KR8GWyjMq=+Mcvz5Zrj0EffNrGrw@mail.gmail.com>
On Fri, Jun 30, 2017 at 09:00:14AM +0300, Сергей Шестаков wrote:
Show 14 quoted lines
> 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?

Previous: Сергей ШестаковNext: Matthieu Moy
Message 2 of 9 in “Bug with automated processing of git status results”
  1. Сергей ШестаковJun 30, 2017
  2. Konstantin KhomoutovJun 30, 2017
  3. Matthieu MoyJun 30, 2017
  4. Torsten BögershausenJun 30, 2017
  5. status: suppress additional warning output in plumbing modesStefan Beller, Jun 30, 2017
  6. Torsten BögershausenJul 1, 2017
  7. Ævar Arnfjörð BjarmasonJul 1, 2017
  8. Junio C HamanoJul 1, 2017
  9. Stefan BellerJul 5, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.