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

discarding refs/original/* after filter-branch (Re: understanding how remote tracking works)

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 9, 2010, 23:07 UTC
Message-ID
<20100809230711.GH4429@burratino>
In-Reply-To
<20100809205309.GA3204@burratino>
Jonathan Nieder wrote:
Show 8 quoted lines
> There are a lot of instances of “rm -r .git/refs/original” after
> running filter-branch, too.  Maybe filter-branch ought to provide
> some synonym for
> 
>  eval "$(
> 	git for-each-ref refs/heads/\* --shell --format='git update-ref -d %(refname) &&' &&
> 	echo :
>  )"
That should have read as
 ...
	git for-each-ref refs/original --shell ...
Sorry about that.
Previous: Jonathan NiederNext: Jonathan Nieder
Message 9 of 11 in “understanding how remote tracking works”
  1. Geoff RussellAug 9, 2010
  2. Ralf EbertAug 9, 2010
  3. Geoff RussellAug 9, 2010
  4. Michael WittenAug 9, 2010
  5. Jonathan NiederAug 9, 2010
  6. Geoff RussellAug 9, 2010
  7. Junio C HamanoAug 9, 2010
  8. Jonathan NiederAug 9, 2010
  9. discarding refs/original/* after filter-branch (Re: understanding how remote tracking works)Jonathan Nieder, Aug 9, 2010
  10. Documentation: add a FILES section for show-refJonathan Nieder, Aug 9, 2010
  11. Junio C HamanoAug 9, 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.