all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 50340@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#50340: Fix remote-location in vc-git-log-incoming
Date: Tue, 19 Oct 2021 20:56:02 +0200	[thread overview]
Message-ID: <87pms0c08t.fsf@gnus.org> (raw)
In-Reply-To: <875yvfurkp.fsf@mail.linkov.net> (Juri Linkov's message of "Sun,  05 Sep 2021 19:36:54 +0300")

Juri Linkov <juri@linkov.net> writes:

>> But this means that my fix worked, because in vc-git-log-incoming
>> I fixed the first command `git fetch`, but it fails in your case
>> in the second command `git log HEAD..upstream`.
>
> If it works for you, go ahead. I just couldn't make the command work
> (patched or not) with either of the projects I tried it on.

[...]

> I'm not sure. This should work for every backend where log-outgoing
> and log-incoming work, right?
>
> Do remotes feature in branch names the same way in Git, Hg and Bzr?

This was a month ago, and skimming it, it wasn't clear to me what the
status here was -- whether this should be worked more on, or whether
Juri's fix should be pushed.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2021-10-19 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 16:16 bug#50340: Fix remote-location in vc-git-log-incoming Juri Linkov
2021-09-02 23:29 ` Dmitry Gutov
2021-09-03  8:12   ` Juri Linkov
2021-09-04  1:50     ` Dmitry Gutov
2021-09-05 16:36       ` Juri Linkov
2021-09-05 19:28         ` Dmitry Gutov
2022-09-23 15:52           ` Juri Linkov
2022-10-02 18:35             ` Juri Linkov
2021-10-19 18:56         ` Lars Ingebrigtsen [this message]
2021-10-19 19:16           ` Juri Linkov

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=87pms0c08t.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50340@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=juri@linkov.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.