unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Zhu Zihao <all_but_last@163.com>
Cc: 55517@debbugs.gnu.org
Subject: [bug#55517] [PATCH]: gnu: emacs-magit: Drop the libgit backend.
Date: Fri, 20 May 2022 22:13:32 -0400	[thread overview]
Message-ID: <87tu9jbpkj.fsf_-_@gmail.com> (raw)
In-Reply-To: <86sfp6je99.fsf@163.com> (Zhu Zihao's message of "Thu, 19 May 2022 13:13:36 +0800")

Hi Zhu,

Zhu Zihao <all_but_last@163.com> writes:

> Fix the typo in commit message
>
>>From 8a2de5764a67bea1cbf789c8d6ce0ab0878ec40b Mon Sep 17 00:00:00 2001
> From: Zhu Zihao <all_but_last@163.com>
> Date: Thu, 19 May 2022 13:01:46 +0800
> Subject: [PATCH] gnu: emacs-magit: Drop the libgit backend.
>
> Drop the libgit backend for following reasons:
>
> 1. The libgit backend of Magitis very incomplete. There's almost no benefits,
> but extra maintenance efforts.

Could you elaborate about "almost no benefits"?  Even if it's a small
benefit, if it makes it faster, I'd still keep it since Magit is at
times excruciatingly slow.

> 2. The libgit backend of Magit can be considered as an extra package. And it's
> still in Proof-Of-Concept status so its quaility doesn't satisfy the
> requirement of Guix package.

There's not really any "quality requirements" for Guix package; we
package stable releases when they're available; the rest is up to us
Guix users.

Do you happen to have a link to some exchange where Magit authors would
recommend against using the libgit library at this point in time to
speed up Magit?  Otherwise, I'm not convinced.

Thanks,

Maxim




  parent reply	other threads:[~2022-05-21  2:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  5:08 [bug#55517] [PATCH]: gnu: emacs-magit: Drop the libgit backend Zhu Zihao
     [not found] ` <handler.55517.B.165293698432676.ack@debbugs.gnu.org>
2022-05-19  5:13   ` [bug#55517] Acknowledgement ([PATCH]: gnu: emacs-magit: Drop the libgit backend.) Zhu Zihao
2022-05-19  6:01     ` Liliana Marie Prikler
2022-05-20  3:52       ` Zhu Zihao
2022-05-20  6:04         ` Liliana Marie Prikler
2022-05-22  9:46           ` Zhu Zihao
2022-05-23  6:46             ` Liliana Marie Prikler
2022-05-28  2:11               ` Zhu Zihao
2022-05-28  6:56                 ` bug#55517: " Liliana Marie Prikler
2022-05-21  2:13     ` Maxim Cournoyer [this message]
2022-05-21  3:45       ` [bug#55517] [PATCH]: gnu: emacs-magit: Drop the libgit backend Zhu Zihao
2022-05-22  0:46         ` Maxim Cournoyer

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=87tu9jbpkj.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=55517@debbugs.gnu.org \
    --cc=all_but_last@163.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).