Skip to content

Keep a persistent carrier object cache - #5

Closed
hmirin wants to merge 2 commits into
format-v5-anonymous-recipientsfrom
carrier-object-cache
Closed

hmirin wants to merge 2 commits into
format-v5-anonymous-recipientsfrom
carrier-object-cache

Conversation

@hmirin

@hmirin hmirin commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

The carrier backend used to re-clone the carrier repository for every
operation. It now keeps a locked cache under
$XDG_CACHE_HOME/git-remote-e2ee/carrier// (override with
GIT_REMOTE_E2EE_CACHE_DIR), fetches only new objects into it, and publishes
from it.

Part of the split of #2; stacked on format-v5-anonymous-recipients.

The carrier backend used to re-clone the carrier repository for every
operation. It now keeps a locked cache under
$XDG_CACHE_HOME/git-remote-e2ee/carrier/<sha256>/ (override with
GIT_REMOTE_E2EE_CACHE_DIR), fetches only new objects into it, and publishes
from it.
`git-e2ee device-add --role read|write|admin` assigns a role. Read-only
devices receive generation keys but cannot author accepted transitions, and
`device-list` shows each device's role.
@hmirin

hmirin commented Oct 14, 2026

Copy link
Copy Markdown
Contributor Author

Landed on main as bf3ffe2 (fast-forward); closed because its stacked base branch moved first.

@hmirin hmirin closed this Oct 14, 2026
@hmirin
hmirin deleted the carrier-object-cache branch October 14, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant