Hello #FediHelp I am trying to create a script using #git in #rustlang
I need to:
- blame (including blaming a file from other commits than the current one)
- show basic information about a commit (sha-1, author, date, commit message)
- iterate on the hunks of the diff introduced by a given commit (hunk with the +/- sign and context)
Should I:
- Shell out and parse the result of git cli output
- use #libgit2 binding
- use #gitoxide if possible, libgit2 when the API I need does not exist yet
Good and quick video but #LetsGetRusty about a new version control manager called #GitOxide. Not quite production ready yet, but it's like Git, just written in Rust.
Rewrite everything in Rust!
Side note, the name seems to refer to rust as a result of oxidation instead of the fungus the language is named after.
I'm excited for the prospect of #Rust being in the #Git project. :)
I would've switched to #gitoxide but it has a shit license.
https://www.phoronix.com/news/GCC-Rust-Developer-Discussion
(yes, the phoronix comments are toxic as they always are)
Used #gitoxide to include the git hash of the HEAD commit in a program at compile time :D
You have to add gix to your [build-dependencies] in Cargo.toml
Well. Using #gitoxide instead of #git (libgit2 specifically) made a MAJOR performance speed up. It's still taking a lot of time, but it takes a lot less time. It's visibly faster this way.
Currently, running yet another flamegraph to make sure I am not spending too much time on something else.
And tomorrow I will figure out resuming things properly.
justsoup 
robinm
Kevin Sullivan
Smol Bean [OLD] (moved to https://evil.social/@shrimple)
Mo Bitar 
MTRNord (they/them)
Brad Larsen
CK's Technology News
