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

Re: Rewriting history with git-filter-branch and leaking objects (?)

From
Sam Vilain <sam@vilain.net>
Date
Aug 19, 2007, 02:34 UTC
Message-ID
<46C7AC3E.5010806@vilain.net>
In-Reply-To
<20070817174621.GA14503@glandium.org>
Mike Hommey wrote:
> Well, with the introduction of git-filter-branch, once you have
> rewritten your history and validated that everything is okay,
> you might mean to remove the original branch...
>

Right, but it's probably better to leave a trail. I tend to use refs/Attic/* for branches that I've re-written (if I published them). That way, nothing will send or receive them by default. Sometimes I'll have a "clean" repository which doesn't have any of them for faster initial cloning.

Sam.
Previous: Mike HommeyNext: Junio C Hamano
Message 4 of 7 in “Rewriting history with git-filter-branch and leaking objects (?)”
  1. Mike HommeyAug 17, 2007
  2. David KastrupAug 17, 2007
  3. Mike HommeyAug 17, 2007
  4. Sam VilainAug 19, 2007
  5. Junio C HamanoAug 17, 2007
  6. Mike HommeyAug 17, 2007
  7. Mike HommeyAug 19, 2007

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.