From: Michael Albinus <michael.albinus@gmx.de>
To: Dima Kogan <dima@secretsauce.net>
Cc: 40670@debbugs.gnu.org
Subject: bug#40670: 28.0.50; Regression: vc-print-log doesn't work with TRAMP because vc-git isn't initialized
Date: Fri, 17 Apr 2020 15:11:48 +0200 [thread overview]
Message-ID: <87tv1ixnmz.fsf@gmx.de> (raw)
In-Reply-To: <874ktj5h54.fsf@shorty.i-did-not-set--mail-host-address--so-tickle-me> (Dima Kogan's message of "Thu, 16 Apr 2020 13:07:19 -0700")
Dima Kogan <dima@secretsauce.net> writes:
> Hi. I'm using a bleeding-edge emacs build from git. Today.
Hi Dima,
> The problem:
>
> 1. emacs -Q
>
> 2. C-x C-f /ssh:host:file
>
> Open any file that lives in a git repo on a remote server
>
> 3. C-x v l
>
> I expect to see the git log for this file, but I get an error: "File
> is not under version control". The modeline doesn't show that emacs
> recognized this as a git file. Also, the only "vc-git-..." function
> that emacs knows about at this point is vc-git-registered. Clearly
> something was supposed to initialize vc-git but that didn't happen.
> As a workaround I CAN do:
>
> 4. C-x v L
>
> This does work to show me the git history of this whole project. This
> loaded vc-git, so I can now go back to the earlier buffer, and C-x v
> l works now
Thanks for the report. I've applied git bisect. Looks like commit
76b3bd8cbb9a0a01941d9c1766c054960e4bfd97 (Improve Tramp cache for
asynchronous processes) has broken Emacs here.
Since I'm the author of that patch, I'll debug. Will report later.
> Thanks!
Best regards, Michael.
next prev parent reply other threads:[~2020-04-17 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 20:07 bug#40670: 28.0.50; Regression: vc-print-log doesn't work with TRAMP because vc-git isn't initialized Dima Kogan
2020-04-17 13:11 ` Michael Albinus [this message]
2020-04-21 11:35 ` Michael Albinus
2020-04-21 23:28 ` Dima Kogan
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=87tv1ixnmz.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=40670@debbugs.gnu.org \
--cc=dima@secretsauce.net \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.