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

Re: How to extract files out of a "git bundle", no matter what?

From
jidanni@jidanni.org <jidanni@jidanni.org>
Date
Dec 19, 2008, 20:13 UTC
Message-ID
<87zlirc49l.fsf@jidanni.org>
In-Reply-To
<494BFCAF.9060703@verizon.net>

SOP> If the bundle requires 0 refs (like above) then you can init a SOP> new repository and should be able to fetch from it:

SOP> git init SOP> git pull bundle.bdl master

Phew, that worked. Thank you!

ML> With relatively recent git (not sure the version), you can just do ML> git clone bundle.bdl Not with git version 1.5.6.5, Debian sid.

Anyway, for man page completeness, I still see the day when:

SOP> You can't just "get the files out". A bundle contains deltas, SOP> where you need the base in order to recreate the file content. SOP> It can't be unpacked in a vacuum.

That is nice by we here at the forensics department of XYZ police force just need to get the files out. We tried "PK UNZIP" but that didn't extract them. We contacted the Computer Science Dept. but that's who they're holding hostage.

SOP> To unpack a bundle you need to clone the project and then fetch SOP> from it:

SOP> git clone src... SOP> git pull bundle.bdl master

That is nice but the perpetrators have destroyed everything except for that one bundle.bdl file, which contains the password to defuse the time bomb.

There must be a way to make a "phony tree" or whatever to "attach to" so extraction can proceed. Be sure to spell it all out on the git-bundle man page as a reference in case some non-computer people need to do aforementioned emergency extraction one day.

Previous: Mark LevedahlNext: Jeff King
Message 4 of 32 in “How to extract files out of a "git bundle", no matter what?”
  1. jidanni@jidanni.orgDec 19, 2008
  2. Shawn O. PearceDec 19, 2008
  3. Mark LevedahlDec 19, 2008
  4. jidanni@jidanni.orgDec 19, 2008
  5. Jeff KingDec 19, 2008
  6. jidanni@jidanni.orgDec 19, 2008
  7. Jeff KingDec 19, 2008
  8. Documentation/git-bundle.txt: Dumping contents of any bundlejidanni@jidanni.org, Jan 1, 2009
  9. Johannes SchindelinJan 1, 2009
  10. Jeff KingJan 1, 2009
  11. jidanni@jidanni.orgJan 1, 2009
  12. Jeff KingJan 1, 2009
  13. jidanni@jidanni.orgJan 2, 2009
  14. Shawn O. PearceJan 2, 2009
  15. Jeff KingJan 2, 2009
  16. jidanni@jidanni.orgJan 2, 2009
  17. git ls-tree prints wacko file sizes if it can't find the blobjidanni@jidanni.org, Jan 1, 2009
  18. jidanni@jidanni.orgJan 1, 2009
  19. Handle sha1_object_info failures in ls-tree -lAlex Riesen, Jan 1, 2009
  20. git-bundle(1): add no references required simplest casejidanni@jidanni.org, Jan 26, 2009
  21. Junio C HamanoJan 26, 2009
  22. git-bundle(1): add no references required simplest casejidanni@jidanni.org, Jan 29, 2009
  23. jidanni@jidanni.orgFeb 1, 2009
  24. Johannes SchindelinFeb 2, 2009
  25. Junio C HamanoFeb 2, 2009
  26. jidanni@jidanni.orgFeb 4, 2009
  27. Junio C HamanoFeb 4, 2009
  28. jidanni@jidanni.orgFeb 4, 2009
  29. git-bundle doc: update examplesNanako Shiraishi, Feb 4, 2009
  30. Jeff KingFeb 4, 2009
  31. Junio C HamanoFeb 4, 2009
  32. Junio C HamanoDec 19, 2008

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.