kc3-lang/libgit2/docs
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
7684a617 | 2025-09-24 14:50:24 | docs: update link to git.git-authors | |
 |
1c6d5114 | 2025-01-07 20:29:44 | docs: add `update_refs` as ABI breaking change In v1.9, we failed to document that `update_refs` was a breaking change. Add information about this change to the ABI breaking changes section. | |
|
1329f1a1 | 2024-12-28 10:02:09 | v1.9: final changelog updates | |
|
a8fbbf77 | 2024-12-28 09:58:25 | Merge pull request #6986 from libgit2/ethomson/warn_sha1 cmake: warn for not using sha1dc | |
|
550cf620 | 2024-12-28 09:49:28 | cmake: warn for not using sha1dc git's hash algorithm is sha1dc, it is not sha1. Per Linus: > Honestly, git has effectively already moved from SHA1 to SHA1DC. > > So the actual known attack and weakness of SHA1 should simply not be > part of the discussion for the next hash. You can basically say "we're > _already_ on the second hash, we just picked one that was so > compatible with SHA1 that nobody even really noticed. Warn users who try to compile with SHA1 instead of SHA1DC. | |
|
3aeb5bd0 | 2024-12-28 08:28:35 | meta: revert soname version update Changing our SONAME / ABI version update policy without an announcement is a breaking change. Provide time to announce a policy update. | |
|
e96e2504 | 2024-12-23 17:05:01 | v1.9: update changelog | |
|
ab0e1606 | 2024-12-16 10:42:44 | docs: include v1.8.4 changelog | |
|
48b63274 | 2024-06-13 19:42:55 | v1.8.2: update changelog | |
|
ae65dac8 | 2024-05-16 00:46:42 | v1.8.1: update changelog |