Probably: - clone (from URL, full or partial) - backup - restore - diff (see which runs are in repo1 vs repo2) - extract (raw log folders from repo) - rebuild (rewrite index -- apply new version of log parser to existing logfiles) - purge (old branches and logs)
Also possible: - rotate (split a subset of old logs into a separate repo) -- inspired by sergiodj's warning that his Git repo experiments became unusably slow after accumulating 1-2 years of buildbot data
Need to make sure existing option '+commit_logs rebuild=yes' will update existing metadata as cleanly as feasible, instead of duplicating old metadata.
On the new master branch, Git-style porcelain to clone/edit/manage the repo would be a nice-to-have wishlist item for me, but it is not enough of a priority to keep this PR open. Closing for the time being.