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

Re: Repo with only one file

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Aug 9, 2013, 10:32 UTC
Message-ID
<5204C546.1030502@viscovery.net>
In-Reply-To
<CAH_OBifYFyVVo_OEfniWJE=0peX+UPLkRznqyQzvO4gGGLu_tQ@mail.gmail.com>
Am 8/9/2013 12:03, schrieb shawn wilson:
> The question still stands though - why is that unassociated commit left there?

Because your command did not remove it. filter-branch does not know that it is "unassociated" when you ask it to follow all commits beginning at HEAD. But when you say 'HEAD -- webban.pl', you ask it to follow only commits that touch webban.pl, which automatically skips that commit.

-- Hannes
Previous: shawn wilsonNext: shawn wilson
Message 9 of 11 in “Repo with only one file”
  1. shawn wilsonAug 7, 2013
  2. Johannes SixtAug 7, 2013
  3. shawn wilsonAug 7, 2013
  4. Phil HordAug 8, 2013
  5. Johannes SixtAug 9, 2013
  6. shawn wilsonAug 9, 2013
  7. Johannes SixtAug 9, 2013
  8. shawn wilsonAug 9, 2013
  9. Johannes SixtAug 9, 2013
  10. shawn wilsonAug 9, 2013
  11. Phil HordAug 9, 2013

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.