From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: guix-devel@gnu.org, guile-user@gnu.org
Cc: Mathieu Othacehe <othacehe@gnu.org>
Subject: Guile-Git 0.6.0 released; looking for maintainers!
Date: Tue, 27 Feb 2024 10:47:34 +0100 [thread overview]
Message-ID: <871q8yjl1l.fsf@inria.fr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1146 bytes --]
Hello!
I’m glad to announce that Guile-Git 0.6.0 has been released, fixing
longstanding issues and adding support for newer libgit2 versions!
https://gitlab.com/guile-git/guile-git/
See ‘NEWS’ file excerpt below.
Incidentally, Guile-Git needs your help! The initial driving force
behind the project is no longer around to help (and I’d like to thank in
particular Erik Edrosa for all their work shepherding the project). We
need new volunteers to help, and new maintainers. If you rely on the
project and/or would like to help, let’s get in touch!
One of the things to look into going further is ABI compatibility.
We’re playing whack-a-mole with ABI/API changes introduced as new
libgit2 versions come out; the ‘check-abi’ target contributed by Sören
Tempel helps in finding glaring ABI mismatches with structs, but it’s
not completely bulletproof either (due to SysV alignment rules, missing
fields etc. are not always uncovered, especially on 64-bit platforms).
An idea might be to look into using nyacc’s ffi-helper to generate
struct definitions.
Happy version control!
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: Type: text/x-org, Size: 1390 bytes --]
* Changes in 0.6.0 (since 0.5.2)
** Updated requirements
Guile-Git now requires libgit2 >= 1.3.0.
** New functionality
*** Support libgit2 up to 1.7.x
*** Support for checkout options
Checkout options can be created with ~make-checkout-options~ and passed
to ~checkout-head~, ~checkout-index~, etc.
*** New ~remote-connect/detached~ procedure
Lets you connect to a detached remote.
*** New ~(git ignore)~ module and ~ignored-file?~ procedure
The ~ignored-file?~ returns true when a file is ignored according to the
ignore rules.
*** New ~owner-validation?~ and ~set-owner-validation!~ procedures
These procedures let you query and set repository directory ownership
validation, which raises an error when attempting to access a repository
not owned by the current user.
*** New ~describe-checkout~ procedure
The procedure returns a pretty description of a checkout, similar to
the ~git describe~ command.
** Bug fixes
*** Always use native endianness when interpreting ~size_t~ pointers
(<https://gitlab.com/guile-git/guile-git/-/issues/20>)
*** Add missing argument to C call made by ~repository-index~
*** Clone-over-SSH tests now ignores =~/.ssh/known_hosts= validation
(<https://gitlab.com/guile-git/guile-git/-/issues/29>)
*** Fix various binary interface incompatibility issues
Running ~make check-abi~ now flags application binary interface (ABI)
issues.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next reply other threads:[~2024-02-27 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 9:47 Ludovic Courtès [this message]
2024-02-27 19:25 ` Guile-Git 0.6.0 released; looking for maintainers! Attila Lendvai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871q8yjl1l.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=othacehe@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).