From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: 50340@debbugs.gnu.org
Subject: bug#50340: Fix remote-location in vc-git-log-incoming
Date: Sat, 4 Sep 2021 04:50:35 +0300 [thread overview]
Message-ID: <63fb440c-a393-541d-2f92-fe28130c899e@yandex.ru> (raw)
In-Reply-To: <87o89aaxhj.fsf@mail.linkov.net>
On 03.09.2021 11:12, Juri Linkov wrote:
>>> - (vc-git-command nil 0 nil "fetch")
>>> + (vc-git-command nil 0 nil "fetch" (unless (string= remote-location "")
>>> + remote-location))
>>
>> I'm not sure which scenario this fixes (pressing RET after 'C-u C-x v I'
>> works fine here), but it shouldn't hurt either.
>
> It fixes the scenario with a non-default remote. Could you try 'C-u C-x v I'
> and typing the name of a non-default remote in a repo with two remotes?
> I wonder if it already worked, and maybe I have some misconfiguration.
Ah, I see what you are referring to.
But does the feature work then?
With your patch, I can pass some alternative upstream to the command,
and it fails at the end with something like:
fatal: ambiguous argument 'HEAD..upstream': unknown revision or path not
in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
>> So if you have a stable repro (some alternative completing-read-function?),
>> you can go ahead and install.
>
> Regarding the default completing-read-function, the prompt of 'C-u C-x v I'
> doesn't provide completion on remote names. Maybe this should be improved
> as well.
I guess some new backend action ('remote-locations'?) could help with that.
next prev parent reply other threads:[~2021-09-04 1:50 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 [this message]
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
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=63fb440c-a393-541d-2f92-fe28130c899e@yandex.ru \
--to=dgutov@yandex.ru \
--cc=50340@debbugs.gnu.org \
--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.