From f09c427d24a4f504f56e03093da1718bceb9f1b9 Mon Sep 17 00:00:00 2001 From: "Jeffrey C. Ollie" Date: Sun, 23 Aug 2026 20:19:57 -0500 Subject: [PATCH] document cloning with radicle Add a README section covering the Radicle repository ID, `rad clone`, `rad seed`, and attaching an existing clone via the `rad://` remote. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01LxhQqeSS12nGUNG2ithMDq --- README.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/README.md b/README.md index 28b289e..6130793 100644 --- a/README.md +++ b/README.md @@ -49,6 +49,37 @@ exe.root_module.addImport("notmuch", notmuch.module("notmuch")); The module links `libnotmuch` and libc itself, so there is nothing else to add. +## Cloning with Radicle + +The repository is also published on the [Radicle](https://radicle.xyz/) +peer-to-peer network under the repository ID + +``` +rad:zQWqvMomwbxzKg6pd4ktY65B8oyY +``` + +With a local Radicle node running, clone it with: + +```console +$ rad clone rad:zQWqvMomwbxzKg6pd4ktY65B8oyY +``` + +That fetches the repository, checks out the default branch, and starts seeding +it so other peers can fetch from you. To follow the repository without checking +out a working copy, use `rad seed` instead: + +```console +$ rad seed rad:zQWqvMomwbxzKg6pd4ktY65B8oyY +``` + +If you already have a clone from one of the other remotes, you can attach it to +the same Radicle repository instead of cloning again: + +```console +$ git remote add rad rad://zQWqvMomwbxzKg6pd4ktY65B8oyY +$ git fetch rad +``` + ## Usage Opening a database returns a tagged union rather than an error union, because -- 2.51.2