unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: van@scratch.space, 31706-done@debbugs.gnu.org
Subject: bug#31706: Emacs 26.1 unable to visit files in vc-git buffer's links after vc-pull
Date: Wed, 13 Jun 2018 05:30:19 +0300	[thread overview]
Message-ID: <83k1r34dvo.fsf@gnu.org> (raw)
In-Reply-To: <20180612202350.GD889@breton.holly.idiocy.org> (message from Alan Third on Tue, 12 Jun 2018 21:23:50 +0100)

> Date: Tue, 12 Jun 2018 21:23:50 +0100
> From: Alan Third <alan@idiocy.org>
> Cc: van@scratch.space, 31706-done@debbugs.gnu.org
> 
> > But the commits are quite safe, don't you think?  And fix a
> > long-standing problem.  So I see no reason not to backport.
> 
> Yes, I think I was just misunderstanding the status of the emacs-26
> branch.
> 
> I’ve pushed them to emacs-26.

Thanks.





      reply	other threads:[~2018-06-13  2:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04  8:26 bug#31706: Emacs 26.1 unable to visit files in vc-git buffer's links after vc-pull Van L
     [not found] ` <handler.31706.B.152810079227439.ack@debbugs.gnu.org>
2018-06-04  8:49   ` bug#31706: Acknowledgement (Emacs 26.1 unable to visit files in vc-git buffer's links after vc-pull) Van L
2018-06-04 15:51 ` bug#31706: Emacs 26.1 unable to visit files in vc-git buffer's links after vc-pull Eli Zaretskii
2018-06-05  3:43   ` Van L
2018-06-05 14:25     ` Eli Zaretskii
2018-06-05 15:07       ` Van L
2018-06-07 20:52       ` Alan Third
2018-06-08  6:39         ` Eli Zaretskii
2018-06-10 15:35           ` Alan Third
2018-06-10 16:09             ` Eli Zaretskii
2018-06-10 20:14               ` Alan Third
2018-06-11  2:27                 ` Eli Zaretskii
2018-06-12 20:23                   ` Alan Third
2018-06-13  2:30                     ` Eli Zaretskii [this message]

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k1r34dvo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31706-done@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=van@scratch.space \
    /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/emacs.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).