-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
gitoxide in cargo #106
Labels
C-integrate-gitoxide
"Oxidize" crates even more by replacing git2 with gitoxide
Projects
Comments
Byron
added
the
C-integrate-gitoxide
"Oxidize" crates even more by replacing git2 with gitoxide
label
Apr 24, 2022
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a fun research project to potentially drive feature development one day to allow replacing git2 with gitoxide.
In order to migrate, not all features would have to be present at first at the cost of compiling both gitoxide and git2 (Something which probably should be avoided).
Features used
worktree
andsubmodule
APIs are similar.git status
(requires index comparison with working tree and head to index)file
protocol #734git
, and it's about reducing the amount of pack files which we can already do pretty well I think, and loose objects could be included in the pack as well (even though undeltified)fetch.unpackLimit
to keep repositories clean (cargo
runs gc occasionally as well)git2::Cred::default()
)gitoxide
must build (and be tested on) 32 bit systemsShortcomings of
gitoxide
in comparison togit2
git
binary forfile://
protocol due to lack of nativeupload-pack
functionality. Remedy is planned with Rust Foundation grant (stretch goal)ssh
binary forssh
connectionNote that replacing clone/fetch related features is tracked in #449 .
Locations and purpose
cd cargo && rg git2:: -l
Potential issues
The text was updated successfully, but these errors were encountered: