Hello,

> The point is to have an actionable bug tracker and not some spaghetti
> thread where it is hard to follow between the still accurate and the
> already fixed.
> 
> Ricardo opened an issue tracked as #30434.
> 
>     Subject: bug#30434: magit won’t work over TRAMP
>     Date: Mon, 12 Feb 2018 13:53:22 +0100 (5 years, 31 weeks, 5 days ago)
> 
> Closed by Mark with the message:
> 
>     Agreed.  Done, in commit 5fe9ba59ba1cea12a70d011aacbace52e3bfda18 on
>     master and commit 317e8e9404058af35d9843e076934560f95d895a on
>     core-updates.  I'm closing this bug now.
> 
>     Date: Wed, 14 Feb 2018 08:52:02 +0000 (5 years, 31 weeks, 3 days ago)
> 
> And the discussion ends on:
> 
>     Date: Fri, 16 Feb 2018 14:00:50 -0500 (5 years, 31 weeks, 1 day ago)
> 
> Then, years later you unarchive and reopen.
> 
>     Date: Wed, 18 May 2022 15:36:02 +0200 (1 year, 18 weeks, 1 day ago)
> 
>     unarchive 30434
>     reopen 30434
> 
> directly followed by Maxim’s question:
> 
>     Why did you reopen that issue?  Does the original problem still affect
>     you (a hard-coded magit-git-executable causing problems when executed on
>     remote machines via TRAMP).
> 
> And this bug was still open just as a reminder waiting for your patch.
> The initial issue had been closed and what you are reporting is not an
> issue anymore, from my understanding.  I am proposing to open a fresh
> issue with accurate information from current Guix revisions about what
> you consider is this bug – referencing to this one if needed.

AFAICT, the issue seems resolved and I doubt any patch will sprout
anymore from this thread.

Closing. Of course, anyone can reopen it if necessary.

> 1: [bug#59253] [PATCH] gnu: emacs-magit: Substitute git executable path.
> Kyle Meyer <k...@kyleam.com>
> Mon, 14 Nov 2022 19:52:36 -0500
> id:87cz9pvy23....@kyleam.com
> https://issues.guix.gnu.org//59253
> https://issues.guix.gnu.org/msgid/87cz9pvy23....@kyleam.com
> https://yhetil.org/guix/87cz9pvy23....@kyleam.com

Regards,
-- 
Nicolas Goaziou





Reply via email to