Linus wrote Git in about 10 days, so I asked my local LLM to build something similar with one promptRich Edmonds writes that he tasked a local LLM with building a Git-like version control system from scratch to test the capabilities of home-based models. Using a 27B parameter Qwen model on a modest 20 GB VRAM setup, the system generated a working Python script named tinyvcs that handles core repository functions like initialization, commits, and history inspection. While the model identified and fixed several bugs on its own, it eventually required manual intervention to correct schema validation and symlink issues, producing a functional but basic proof of concept that lacks features like branching and remote management.
- The hardware utilized for this project is being used for a non-intended purpose, as consumer-grade GPUs are generally designed for gaming and graphics rendering rather than the heavy lifting required for local model inference.
- The LLM was strictly constrained to the Python standard library and had no internet access or ability to call external APIs.
- The resulting tinyvcs tool is comparable to an early prototype of Git, featuring content-addressed objects and SHA-based IDs but missing standard features like tags, remotes, and merging.
- The hardware utilized for this project is being used for a non-intended purpose, as consumer-grade GPUs are generally designed for gaming and graphics rendering rather than the heavy lifting required for local model inference.
- The LLM was strictly constrained to the Python standard library and had no internet access or ability to call external APIs.
- The resulting tinyvcs tool is comparable to an early prototype of Git, featuring content-addressed objects and SHA-based IDs but missing standard features like tags, remotes, and merging.
This article explores the most significant features and updates introduced in Git versions 2.53 and 2.54, highlighting improvements to repository management, history rewriting, and configuration flexibility.
Key highlights include:
- The new experimental git history command for targeted rewrites like reword and split.
- Config-based hooks that allow defining Git hooks in configuration files rather than just the .git/hooks directory.
- Geometric repacking becoming the default strategy during manual maintenance to improve efficiency.
- Improvements to git add -p usability and the maturation of the experimental git replay command.
- Enhanced HTTP transport handling for 429 Too Many Requests responses.
- Compatibility updates for git log -L with pickaxe searches and patch formatting.
- Support for non-ASCII characters in Git aliases through a new subsection-based syntax.
Key highlights include:
- The new experimental git history command for targeted rewrites like reword and split.
- Config-based hooks that allow defining Git hooks in configuration files rather than just the .git/hooks directory.
- Geometric repacking becoming the default strategy during manual maintenance to improve efficiency.
- Improvements to git add -p usability and the maturation of the experimental git replay command.
- Enhanced HTTP transport handling for 429 Too Many Requests responses.
- Compatibility updates for git log -L with pickaxe searches and patch formatting.
- Support for non-ASCII characters in Git aliases through a new subsection-based syntax.
Agent Trace is an open specification for tracking AI-generated code, providing a vendor-neutral format for recording AI contributions alongside human authorship in version-controlled codebases.
A discussion on how to commit partial changes in Emacs, likely focusing on techniques and tools for version control integration within the Emacs environment.
Plandex is an AI coding agent designed to work directly in the terminal, capable of planning and completing large tasks that span many files and steps. It helps developers build new apps quickly, add features to existing codebases, write tests and scripts, understand code, and fix bugs.
