From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>, Wojtek Kosior <koszko@koszko.org>
Cc: Philip McGrath <philip@philipmcgrath.com>, guix-devel@gnu.org
Subject: Re: RFC: libgit2 is slow/inefficient; switch to git command?
Date: Wed, 23 Nov 2022 10:57:55 +0100 [thread overview]
Message-ID: <86tu2qat7g.fsf@gmail.com> (raw)
In-Reply-To: <87k03mu1w5.fsf@beadling.co.uk>
Hi,
On Tue, 22 Nov 2022 at 21:15, Phil <phil@beadling.co.uk> wrote:
> Just to add mine too - libgit2 behaves differently to command-line git
> in ways which can make guix do unexpected things when caching clones in
> certain cases. This has resulted in some hard to diagnose issues with
> using guix to build PRs for example.
[...]
> An explanation of why, was raised with libgit2:
> https://github.com/libgit2/libgit2/issues/6183
To avoid people to follow various links, this issue #6183 is another
manifestation of issue #3361 (still open since Aug 6, 2015). Quoting:
Git has recently changed the refspec matching rules to allow
refspecs such as
refs/heads/o*:refs/remotes/heads/i*
We still perform checks using the old rules by which the glob
must always match a full path element.
https://github.com/libgit2/libgit2/issues/3361
However, pleas note that only 3 issues with the tag ’git compatibility’
are currently open [1]–well three when 2 are related.
1: <https://github.com/libgit2/libgit2/labels/git%20compatibility>
Cheers,
simon
next prev parent reply other threads:[~2022-11-23 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 2:21 RFC: libgit2 is slow/inefficient; switch to git command? Maxim Cournoyer
2022-11-22 15:39 ` zimoun
2022-11-22 16:49 ` Philip McGrath
2022-11-22 17:51 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2022-11-22 21:15 ` Phil
2022-11-23 9:57 ` zimoun [this message]
2022-11-23 22:04 ` Ludovic Courtès
2022-11-23 22:16 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86tu2qat7g.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=koszko@koszko.org \
--cc=phil@beadling.co.uk \
--cc=philip@philipmcgrath.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).