ByronBates

5 ms·

1.
by ByronBates 4y ago
You could try the alternative version of the database-generator: https://github.com/jmforsythe/Git-Heat-Map/pull/6 - it shouldn't crash.
2.
by ByronBates 4y ago
Computing diffs is what takes large amounts of time as the object database is used intensively along with limited efficiency of object caches. I couldn't resist and threw `gitoxide` at it, and it turned out to be more than 2x as fast (
3.
by ByronBates 4y ago
`gitoxide` can currently perform many of the tasks required, and closing the loop for a full clone with worktree is going to happen at the end of this year. That said, here is how to receive a pack from the remote and resolve it: `mkdir out
4.
by ByronBates 4y ago
That number is already based on using `zlib-ng`. Sometimes I wonder if it's cheating since `git` might not actually use it. In any case, improving the efficiency of `zlib` along with the Rust integration for it has immediate impact on
5.
by ByronBates 4y ago
> This is fast enough for small repositories, but as the repository increases in size the overhead of parsing these plain-text files to get the graph relationships becomes too expensive. Even the fact that we need a binary search to loca
6.
Check out the Linux kernel in less than a second with gitoxide(github.com)
2 points by ByronBates 5y ago|0 comments
7.
by ByronBates 6y ago
I frequently use `tig` to see the commit history, and pull out a single commit hash for use in `git checkout` or to reference it elsewhere. Probably it's just me not knowing all the `tig` hotkeys to make that easy, but it's my hop
8.
by ByronBates 6y ago
It's a project goal to make the API so accessible and easy to use, that's it's straightforward to quickly throw together your very own custom commands that do exactly what you need. This should allow building these slot-in co
9.
by ByronBates 6y ago
Great point! Windows is already tested on CI, but I used the opportunity to make Windows support explicit in the project goals.
10.
by ByronBates 6y ago
I am not interested in competing with libgit2, and have no plans in adding and maintaining C-bindings to the project. This doesn't mean, however, that other parties couldn't maintain them out-of repo at first, and once things stab
11.
by ByronBates 6y ago
That sounds like such a project should definitely see improvements when using GitOxide. Even in projects of the size of the Linux Kernel checkouts can take time as those only reach about 3000 files per second. You will see only 70% of a sin
12.
by ByronBates 6y ago
Right now, the project is clearly missing contribution guidelines, but now that it's a bit more public these will be added soon, possibly along with some tickets that are ready for pickup. For now I am very focussed on implementation.
13.
by ByronBates 6y ago
Let me reply with the most tedious parts, as I wouldn't want to make the impression of labelling git as 'bad' - I have been fascinated by it for more than 10 years now and it's time to scratch my itch for good. Please no
14.
by ByronBates 6y ago
Absolutely! My plan is to proclaim a version 1.0 once the basic workflow of clone-commit-push can be performed, which should be enough for many to start using it. From that point on, the API should remain stable, following semantic versioni
15.
by ByronBates 6y ago
As this is part of the every-day workflow, I will think long and hard on how to make it as painless and user-friendly as possible. Having a more user-friendly experience on the command-line is one of the project goals, and it will also be m
16.
by ByronBates 6y ago
Unfortunately I can't yet tell, as the corresponding code does not yet exist. Object and pack lookup is competitively fast so I would hope that translates well to everyday operations like that. Actual numbers for what's there, pac
17.
by ByronBates 6y ago
I am the author, and will be here for a few hours in case there are any questions. (proof: https://keybase.io/byronbates )
18.
by ByronBates 8y ago
The same author also wrote hyperfine, a tool to compare performance of various program runs. hyperfine './target/release/hexyl ./target/release/hexyl' 'xxd ./target/release/h