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

Re: Bug with automated processing of git status results

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jun 30, 2017, 09:09 UTC
Message-ID
<vpqr2y1u9j2.fsf@anie.imag.fr>
In-Reply-To
<CAM1TZMGXiDpzt3uhpDaE41KR8GWyjMq=+Mcvz5Zrj0EffNrGrw@mail.gmail.com>
Сергей Шестаков <s_shestakov@playrix.com> 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/
Previous: Konstantin KhomoutovNext: Torsten Bögershausen
Message 3 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.