From: Alex Kost <alezost@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 30434@debbugs.gnu.org
Subject: bug#30434: magit won’t work over TRAMP
Date: Thu, 15 Feb 2018 22:38:56 +0300 [thread overview]
Message-ID: <87po56avqn.fsf@gmail.com> (raw)
In-Reply-To: <877erfph9m.fsf@netris.org> (Mark H. Weaver's message of "Wed, 14 Feb 2018 13:17:57 -0500")
Mark H Weaver (2018-02-14 13:17 -0500) wrote:
> Hi Alex,
>
> Alex Kost <alezost@gmail.com> writes:
>
>> Mark H Weaver (2018-02-14 03:51 -0500) wrote:
>>
>>> Ricardo Wurmus <rekado@elephly.net> writes:
>>>> I think it makes sense *not* to hardcode the path to the git executable
>>>> here.
>>>
>>> Agreed. Done, in commit 5fe9ba59ba1cea12a70d011aacbace52e3bfda18 on
>>> master and commit 317e8e9404058af35d9843e076934560f95d895a on
>>> core-updates. I'm closing this bug now.
>>
>> You didn't remove "git" from the inputs. I think it is not needed now.
>
> I removed it on my first attempt, but the build failed. See below.
Oh, right, sorry. I use my own package for magit and it dosn't require
git input, so I thought that the original guix package also doesn't need
it. Sorry for the confusion :-)
--
Alex
next prev parent reply other threads:[~2018-02-15 19:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <365299e60040c03a84cbb7770adb3f94349dd2ed.camel@telenet.be>
2018-02-12 12:53 ` bug#30434: magit won’t work over TRAMP Ricardo Wurmus
2018-02-12 17:33 ` Alex Kost
2018-02-12 19:11 ` Ricardo Wurmus
2018-02-14 8:51 ` Mark H Weaver
2018-02-14 17:00 ` Alex Kost
2018-02-14 18:17 ` Mark H Weaver
2018-02-15 19:38 ` Alex Kost [this message]
2018-02-16 9:09 ` Mark H Weaver
2018-02-16 16:56 ` Alex Kost
2018-02-16 19:00 ` Mark H Weaver
2018-02-12 19:51 ` Mark H Weaver
[not found] ` <handler.x.B30434.165288084625349.unknown@debbugs.gnu.org>
[not found] ` <77826704875d168a2f7c608e146d9d5b09e7588c.camel@telenet.be>
2022-07-13 12:53 ` Maxim Cournoyer
2022-07-20 15:42 ` Maxime Devos
2022-07-21 4:04 ` Maxim Cournoyer
2023-09-21 7:34 ` Simon Tournier
2023-09-23 10:17 ` Maxime Devos
2023-09-23 10:19 ` Maxime Devos
2023-09-23 11:47 ` Simon Tournier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po56avqn.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=30434@debbugs.gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.