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

Re: Replacing large blobs in git history

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 7, 2012, 21:27 UTC
Message-ID
<CACBZZX4hinV8vkebyNCLp_Ac6L80aNbdGOFqg1nSsCuRktFFrg@mail.gmail.com>
In-Reply-To
<4F56786D.60801@gmail.com>
On Tue, Mar 6, 2012 at 21:49, Neal Kreitzinger <nkreitzinger@gmail.com> wrote:
Show 6 quoted lines
> On 3/6/2012 10:09 AM, Barry Roberts wrote:
> Be aware that you are rewriting history.  I assume this is published
> history that you are going to run filter-branch on.  That means everyone who
> cloned from the old history (pre-filter-branch), not to mention those who
> also have WIP based on the old history, will need to somehow adjust to the
> new history.

Does something other than git-fsck actually check whether the collection of blobs you're getting from the remote when you clone have sensible sha1's?

What'll happen if he replaces that 550MB blob with a 0 byte blob but hacks the object store so that it pretends to have the same sha1?

Of course the real solution to this issue is to either rewrite history, or to change Git to support partially fetching the old blobs in your project.

Previous: Neal KreitzingerNext: Holger Hellmuth
Message 3 of 6 in “Replacing large blobs in git history”
  1. Barry RobertsMar 6, 2012
  2. Neal KreitzingerMar 6, 2012
  3. Ævar Arnfjörð BjarmasonMar 7, 2012
  4. Holger HellmuthMar 8, 2012
  5. Junio C HamanoMar 8, 2012
  6. Michael HaggertyMar 7, 2012

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.