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

Re: [PATCH] Improve git-prune -n output

From
Junio C Hamano <junkio@cox.net>
Date
Nov 3, 2006, 02:40 UTC
Message-ID
<7vslh1l0bj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200611021112.26420.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> writes:
Show 9 quoted lines
> prune_object() in show_only mode would previously just show the path to the
> object that would be deleted.  The path the object is stored in shouldn't be
> shown to users, they only know about sha1 identifiers so show that instead.
>
> Further, the sha1 alone isn't that useful for examining what is going to be
> deleted.  This patch also adds the object type to the output, which makes it
> easy to pick out, say, the commits and use git-show to display them.
>
> Signed-off-by: Andy Parkins <andyparkins@gmail.com>
List members and git users, 
	if you are using "prune -n" output in your scripts, this
change could cause those scripts to break; so please holler.

I am inclined to take this output format change, so if you are going to holler please do so fast.

Previous: Andy Parkins
Message 2 of 2 in “Improve git-prune -n output”
  1. Improve git-prune -n outputAndy Parkins, Nov 2, 2006
  2. Junio C HamanoNov 3, 2006

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.