Skip to content

Version control awareness #263

Answered by hendrikvanantwerpen
ghost asked this question in Q&A
Discussion options

You must be logged in to vote

Hi! The library is certainly designed to fit an incremental model compatible with version control. However, there is no provided orchestration for that. Let me elaborate.

The overall idea is along the lines that you suggest.

  1. For each blob in a commit, construct a stack graph and compute partial paths. Store these.

  2. Resolve references using path stitching. The path stitcher is phased, and the result of the previous phase can be used to lazy load partial paths that may be relevant for the next phase.

This approach becomes nicely incremental when the results from (1) are stored based on the Git blob oid. If a blob doesn't change from one commit to the next, its blob oid will be the same…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@ghost
Comment options

Answer selected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant