Using Git Offline

Original Article ↗ Hacker News Discussion ↗

Git’s distributed design enables fully offline and air‑gapped workflows, from treating local folders, USB drives, and LAN shares as remotes to moving changes via `git bundle` or email patches instead of relying on GitHub or other hosted forges. Commenters contrast this with today’s largely centralized pull‑request culture, debating trade‑offs between convenience, a “single source of truth,” and truly decentralized collaboration models such as mailing lists or federated forges. They also highlight broader uses—backing up configs, manuscripts, and game servers—and note alternatives like git‑annex and Fossil for large files or single‑file repository portability.

Using Git Offline & Local Remotes

  • Many use Git entirely offline for private notes, configs, or in air‑gapped environments.
  • Remotes can be simple file paths: USB sticks, local folders, network shares, NAS, or another machine over SSH.
  • Bare repos on LAN machines serve as backup and sync hubs; multiple remotes (GitHub, LAN, USB, etc.) can coexist.
  • Local clones may share storage via hard links, so multiple clones don’t necessarily duplicate blob data.
  • git bundle and patch-based workflows (format-patch, am, send-email) are highlighted as tools for moving changes without live connectivity.

Distributed vs Centralized Use

  • Many treat Git as “remote storage” (like SCP), ignoring its distributed nature.
  • Humans gravitate to a single “source of truth” (e.g., GitHub main branch), even though every clone is equivalent in principle.
  • Some argue true distribution just means any peer can be the integration point; others insist you still end up with at least one authoritative release branch.
  • Debate over PRs: functionally decentralized (everyone has a fork) but operationally centralized because PRs and accounts live on a single forge, often GitHub.

Email/Patch-Based Collaboration

  • Several comments emphasize Git’s original email/patch workflow: contributors send patches via mailing lists; maintainers apply and forward them up a hierarchy.
  • Advantages cited: natural decentralization, no need for accounts on multiple forges, and resilient distribution of “PRs” via email infrastructure.
  • Criticisms: harder to track what’s applied, long email threads can resemble unwieldy PRs, and many prefer centralized web tools for convenience.

Broader Uses, Tools, and Alternatives

  • Git is described as foundational and useful beyond code: resumes, novels, game servers, system configs, etc.
  • Questions and suggestions around using Git for file sync; limitations for large files noted, with git-annex and git‑LFS mentioned.
  • Alternatives like Fossil are praised for offline and all‑in‑one workflows (single SQLite repo, built‑in web UI, issues, wiki).
  • Some nostalgia for fully decentralized SSH-based setups contrasts with today’s preference for hosted platforms (GitHub, GitLab, Bitbucket).