Converting shallow Git bundles into normal repositories
The article discusses the process of converting a shallow Git bundle into a normal repository. It outlines the steps required to initialize a bare repository, extract and index the packfile, and set the reference to the appropriate object ID. The author suggests that the bundle format could benefit from improvements to better communicate shallowness.
- ▪The process begins by initializing a bare repository with a specified object format.
- ▪Next, the packfile is extracted and indexed to create necessary files for the repository.
- ▪Finally, the reference is set to the object ID, and the shallow commit is indicated.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Runxiyu |
| Canonical URL | https://runxiyu.org/comp/shallowbundle/ |
| Publication time | Wed, 27 May 2026 05:02:10 -0500 |
| Retrieval time | 2026-05-27T10:07:58.288Z |
| Last seen | 2026-05-27T10:07:58.288Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | xytEDiPIvRZG |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Let’s say you have a shallow Git bundle, i.e., not all referenced objects are present. How do you convert it into a normal shallow repository? Initialize the target as a bare-repo with your desired object-format. git init --bare --object-format=sha1 target.git && cd target.git Find the start of the pack in each bundle (version 2 packs starts with 5041 434b 0000 0002). In my case it’s byte offset 77. Extract and index the packfile, creating the .idx and .rev. tail -c +77 ../source.bundle | git index-pack --stdin Extract the ref OID and ref name from the bundle. oid="$(git bundle list-heads source.bundle | awk '{print $1}')" ref="$(git bundle list-heads source.bundle | awk '{print $2}')" Set the ref to the OID, and set HEAD to the ref.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Runxiyu.
Discussion
0 commentsMore from Runxiyu
