Repository Clone

• git-config
  • A complete implementation, writing a the git remote configuration is needed for finalizing the clone
• git-ref
  • create ref pointing to ID
    • assure to keep the path towards symbolic refs open, and allow specifying if these should be followed or not
• git-repository
  • instance for a valid looking repository
    • support shallow repos/references
  • create-update refs as received from clone/git-receive-pack
• gix clone
  • try initializing repo on output path - if so, use that to learn about pack location and place new pack there, allow Repo to create refs somehow.
    • _probably this is done using the repository itself, which steers the whole process and injects it's own delegates.
  • otherwise create the scaffolding needed for a new repository, probably based on init implementation
• receive pack
  • resolve thin pack with Bundle
• git-repository
  • clone from https remote

FSCK an entire repository

• multi-db (incorporate object lookup for loose objects and packs)
  • single threaded
  • optional object cache
  • fs-check - verify all object content of a git repository

Commit-Graph

• A plumbing command to extract some value from the current implementation, maybe statistics, or verification

• Application of the command above in a stress test

• Questions

  • What to do with the 'extra-garbage', some code is commented out.

Other

To be picked in any order….

• prodash
  • finish transitioning to futures-lite to get rid of futures-util dependency to reduce compile times
• criner
  • upgrade to prodash 9.0
  • switch to isahc or ureq (blocking, but could use unblock for that) seems to allow async-reading of bodies, allowing to get rid of reqwest and tokio. Redirect is configurable.