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 26, 2012, 22:46 UTC
Message-ID
<7vhayddxgp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vty2ddzqj.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 7 quoted lines
> I think that both the ultimate goal explained above, and the direction in
> which the documentation updates tries to move us, are good.  I only gave a
> cursory look at the code changes, but what they implement seems to match
> the intention.
>
> Of course I may be missing something, so objections from others to argue
> why we shouldn't do this is very much welcomed to stop me and Clemens ;-).
Let's start with the obvious.

It is much easier for a user to use a new option on the command line when he wants to use an improved behaviour when he runs the command manually. Having to update scripts that run the command to act on its output, on the other hand, is much more painful to the users.

And the intended audience for this change clearly is interactive users that follow the user-manual to try things out.

Given that, isn't it not just sufficient but actually better to instead add a new --no-dangling option and keep the default unchanged?

Previous: Junio C HamanoNext: Zbigniew Jędrzejewski-Szmek
Message 3 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.