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

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

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 28, 2006, 14:00 UTC
Message-ID
<ehvnob$tmj$1@sea.gmane.org>
In-Reply-To
<200610270937.11368.andyparkins@gmail.com>
Andy Parkins wrote:
> 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.
This allowed to 'rm -f' [some] of what git-prune -n shows.
Did anybody used that? I don't know...
> 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.

Well, you can always use git-lost-found. Perhaps it would be better to add -n option to git-lost-found to not create refs in $GIT_DIR/lost-found/ directory.

Sorry for being late with that suggestion.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Andy ParkinsNext: Junio C Hamano
Message 5 of 10 in “Improve git-prune -n output”
  1. Improve git-prune -n outputAndy Parkins, Oct 26, 2006
  2. Junio C HamanoOct 26, 2006
  3. Andy ParkinsOct 26, 2006
  4. Improve git-prune -n outputAndy Parkins, Oct 27, 2006
  5. Jakub NarebskiOct 28, 2006
  6. Junio C HamanoOct 28, 2006
  7. Andy WhitcroftOct 26, 2006
  8. Petr BaudisOct 27, 2006
  9. Andy ParkinsOct 27, 2006
  10. Junio C HamanoOct 27, 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.