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

Re: [PATCH] fsck: do not print dangling objects by default

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 27, 2012, 21:34 UTC
Message-ID
<7vhayc55a7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120227211316.GA29081@ecki>
Clemens Buchacher <drizzd@aon.at> writes:
> There is something wrong with weighting a UI improvement against
> convenient use in scripts. If that were the issue, then ...

But that is not the issue. Nobody said anything about convenience for script writers.

I am talking about regressions to already written long time ago and used by many people _without_ them having to worry about how it internally works. By switching the default, you are suddenly making them worry about it again.

Previous: Clemens BuchacherNext: Junio C Hamano
Message 10 of 11 in “fsck: do not print dangling objects by default”
  1. fsck: do not print dangling objects by defaultClemens Buchacher, Feb 26, 2012
  2. Junio C HamanoFeb 26, 2012
  3. Junio C HamanoFeb 26, 2012
  4. Zbigniew Jędrzejewski-SzmekFeb 27, 2012
  5. Jeff KingFeb 27, 2012
  6. Junio C HamanoFeb 27, 2012
  7. Clemens BuchacherFeb 27, 2012
  8. Jeff KingFeb 27, 2012
  9. Clemens BuchacherFeb 27, 2012
  10. Junio C HamanoFeb 27, 2012
  11. fsck: --no-dangling omits "dangling object" informationJunio C Hamano, Feb 28, 2012

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.