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

Re: [PATCH] fetch: don't output non-errors on stderr

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Jun 26, 2010, 15:07 UTC
Message-ID
<AANLkTikxJ_MDLhQFweRMWvhzJy9QIfyuJTYaY4a2tPwS@mail.gmail.com>
In-Reply-To
<AANLkTikq4z5Qs6UUnSh8T9GjVTJBdH8Wy3djIIOlrs2Y@mail.gmail.com>
On Sat, Jun 26, 2010 at 13:40, Tay Ray Chuan <rctay89@gmail.com> wrote:
Show 8 quoted lines
> On Sat, Jun 26, 2010 at 8:14 PM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> But it sounds like we need some general discussion on what stdout and
>> stderr should be used for in Git with regards to progress messages,
>> errors and other similar things.
>
> I'd say - submit a patch for the style guide with your proposed
> guidelines on stdout and stderr usage.

I'm not sure how such a guide should be like for the general case, but at least making commands internally consistent (as this patch does) is one step in that direction.

Previous: Tay Ray ChuanNext: Jeff King
Message 16 of 19 in “Bugreport: Git responds with stderr instead of stdout”
  1. Jack DesertApr 25, 2010
  2. Jacob HelwigApr 25, 2010
  3. Ævar Arnfjörð BjarmasonApr 25, 2010
  4. Jeff KingApr 25, 2010
  5. Ævar Arnfjörð BjarmasonApr 25, 2010
  6. Jeff KingApr 25, 2010
  7. Ævar Arnfjörð BjarmasonJun 12, 2010
  8. fetch: don't output non-errors on stderrÆvar Arnfjörð Bjarmason, Jun 24, 2010
  9. fetch: don't output non-errors on stderrÆvar Arnfjörð Bjarmason, Jun 25, 2010
  10. Junio C HamanoJun 25, 2010
  11. Ævar Arnfjörð BjarmasonJun 25, 2010
  12. Junio C HamanoJun 25, 2010
  13. Jeff KingJun 26, 2010
  14. Ævar Arnfjörð BjarmasonJun 26, 2010
  15. Tay Ray ChuanJun 26, 2010
  16. Ævar Arnfjörð BjarmasonJun 26, 2010
  17. Jeff KingJun 26, 2010
  18. Ævar Arnfjörð BjarmasonJun 26, 2010
  19. Jack DesertApr 25, 2010

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.