git-date
libgit2
git-date | libgit2 | |
---|---|---|
- | 30 | |
6 | 9,643 | |
- | 0.6% | |
0.0 | 9.7 | |
over 6 years ago | 2 days ago | |
C | C | |
GNU General Public License v2.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-date
We haven't tracked posts mentioning git-date yet.
Tracking mentions began in Dec 2020.
libgit2
-
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
Everything that is replicated on the network is stored as a Git object, using the libgit2[0] library. This library uses hardened SHA-1 internally, which is called sha1dc (for "detect collision").
[0]: https://github.com/libgit2/libgit2/blob/ac0f2245510f6c75db1b...
-
Speedbump – a TCP proxy to simulate variable network latency
This is delightful and I can't wait to try it out. Right now, the libgit2 project (https://github.com/libgit2/libgit2) has a custom HTTP git server wrapper that will throttle the responses down to a very slow rate. It's fun watching a `git clone` running over 2400 baud modem speeds, but it's actually been incredibly helpful for testing timeouts, odd buffering problems, and other things that crop up in weird network environments.
I'd love to jettison our hacky custom code and use something off-the-shelf instead.
- Things I just don't like about Git
-
GitKraken Client Is Migrating from Libgit2 to the Git Executable
I've built a UI on top of libgit2 and I wish that this blog post expanded on which new features are missing (sparse checkout?).
To quote: "The migration to Git Executable will allow us to resolve long-standing issues with GitKraken Client, such as poor LFS performance, SSH configuration support and many other features/performance improvements."
I agree on LFS performance on Windows. SSH config support is a pain due to libssh2 but openssh support is on the way (https://github.com/libgit2/libgit2/pull/6617).
There are many cons to using the Git executable itself (parsing output, error reporting, version handling). Seems to me that there's more to this?
-
Mold 2.0.0
I'm curious about the license change? This is an executable is it not? Invoking it as a separate process does not require you make the software calling it GPL so switching to MIT should have no affect in the common case.
If the authors really wanted a more permissive license, then instead of relicensing from AGPL to MIT they should have gone AGPL with linking exception. An example of a project that does this is libgit2 [1]. This licensing is more permissive but still permits the author to sell commercial licenses to those making closed-source code changes.
[1] https://github.com/libgit2/libgit2#license
- Shadow cloning support landed in libgit2
-
I'm feeling lazy today but want a better excuse than "working on documention" for the morning standup.
Using libxlsxwriter and libgit, it's straightforward -- just putting the equivalent of git shortlog and lines added and removed into a line of cells.
- libgit2 fails to verify SSH keys by default
What are some alternatives?
git-object - Git object and its parser
pygit2 - Python bindings for libgit2
git - git protocol and storage in pure haskell
elfshaker - elfshaker stores binary objects efficiently
git-config - A simple parser for Git configuration files.
git-branchless - High-velocity, monorepo-scale workflow for Git
git-fmt - WIP: A custom git command for formatting code
horde - Horde is a distributed Supervisor and Registry backed by DeltaCrdt
restless-git - Haskell library for easy Git serialization
git2-rs - libgit2 bindings for Rust
git-vogue - Make your Haskell git repositories fashionable.
pygooglenews - If Google News had a Python library