From: Zhu Zihao <all_but_last@163.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 55427@debbugs.gnu.org
Subject: bug#55427: emacs-libgit tests are broken
Date: Wed, 18 May 2022 21:17:42 +0800 [thread overview]
Message-ID: <86wnejm0qw.fsf@163.com> (raw)
In-Reply-To: <8913b7de248eb03b468c3ca3fb85f5f749884169.camel@ist.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
>> magit will still work with the git executable if there's no
>> emacs-libgit.
>>
>> Any thoughts?
> I don't see any benefits in this approach, do you?
>
> [1] http://ci.guix.gnu.org/build/859957/details
I don't see any benefits on libgit implementation.
The only method supported by libgit backend is `magit-bare-repo-p`[1],
magit use git executable to do 99.9% works.
The libgit backend should be a separated package. There's
https://github.com/magit/magit/blob/master/lisp/magit-libgit-pkg.el for
it. Its quaility is poor because it's currently in POC status and the
development status has been put on hold indefinitely.[2]
[1] https://github.com/magit/magit/blob/master/lisp/magit-libgit.el#L79
[2] https://github.com/magit/magit/issues/2959#issuecomment-1112185169
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-05-18 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 11:19 bug#55427: emacs-libgit tests are broken Liliana Marie Prikler
2022-05-16 10:01 ` Zhu Zihao
2022-05-17 15:14 ` Zhu Zihao
2022-05-17 23:10 ` Kyle Meyer
2022-05-18 6:14 ` Liliana Marie Prikler
2022-05-18 13:17 ` Zhu Zihao [this message]
2022-05-18 10:02 ` Maxime Devos
2022-05-18 13:13 ` Zhu Zihao
2022-05-18 13:24 ` Maxime Devos
2022-05-18 13:30 ` Maxime Devos
2022-05-18 15:34 ` Zhu Zihao
2022-05-18 22:44 ` Kyle Meyer
2022-05-16 10:28 ` Taiju HIGASHI
2022-05-16 10:40 ` Taiju HIGASHI
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=86wnejm0qw.fsf@163.com \
--to=all_but_last@163.com \
--cc=55427@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/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).