Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing support for parsing and using commit_graph files #1191

Open
kevinhendricks opened this issue Jun 30, 2023 · 0 comments
Open

missing support for parsing and using commit_graph files #1191

kevinhendricks opened this issue Jun 30, 2023 · 0 comments

Comments

@kevinhendricks
Copy link
Contributor

kevinhendricks commented Jun 30, 2023

From fighting with the lcas routines and getting commit times, I looked more into how actual git handles the inherently more unreliable commit times (due to cross repo mishandled time settings). Git uses generation numbers. A generation number is 1 plus the max of your parents generation numbers.p with the original first commit with no parents being 0. To prevent having to walk the full commit history dag, they now calculate these generations once and store it along with commit time and parent info into a commit_graph file (object) than has a very specific format file format that needs to be read in and written out just like an index file.

Having access to this information would make lcas lookup (and therefore merging) much easier.

Do you have any near term plans to add commit-graph file and lookup support to dulwich?

If not, would you be interested in having it contributed?

Thanks,

Kevin

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

No branches or pull requests

1 participant