From: Stefan Kangas <stefan@marxist.se>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Tom Tromey <tom@tromey.com>, 25710@debbugs.gnu.org
Subject: bug#25710: Acknowledgement (25.1.91; vc-retrieve-tag does not offer branch namd completion)
Date: Tue, 11 Aug 2020 00:56:50 -0700 [thread overview]
Message-ID: <CADwFkmmi9YTAxPEE725iPmSyZ4RUC=g7AJ4yX7W8+841_YTFZw@mail.gmail.com> (raw)
In-Reply-To: <94822cdb-159e-133b-a067-8ae8c765b9a6@yandex.ru> (Dmitry Gutov's message of "Mon, 6 Mar 2017 13:42:03 +0200")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 04.03.2017 20:06, Tom Tromey wrote:
>>>>>>> "Dmitry" == Dmitry Gutov <dgutov@yandex.ru> writes:
>> Dmitry> Will it change how vc-git-revision-completion-table works,
>> Dmitry> across all commands? If so, I'm good with it.
>> Yeah. What do you think of the appended?
>
> Looks good, thanks.
That was 3 years ago.
It seems like the patch here was never installed. Should it be?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-11 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 23:11 bug#25710: 25.1.91; vc-retrieve-tag does not offer branch namd completion Tom Tromey
[not found] ` <handler.25710.B.148702752518881.ack@debbugs.gnu.org>
2017-02-14 3:13 ` bug#25710: Acknowledgement (25.1.91; vc-retrieve-tag does not offer branch namd completion) Tom Tromey
2017-02-14 10:24 ` Dmitry Gutov
[not found] ` <87inoczdun.fsf@tromey.com>
2017-02-14 23:31 ` Dmitry Gutov
2017-02-15 4:35 ` Tom Tromey
2017-02-17 1:26 ` Dmitry Gutov
2017-02-17 4:09 ` Tom Tromey
2017-02-19 22:13 ` Dmitry Gutov
2017-03-04 18:06 ` Tom Tromey
2017-03-06 11:42 ` Dmitry Gutov
2020-08-11 7:56 ` Stefan Kangas [this message]
2020-08-11 19:44 ` Dmitry Gutov
2020-08-19 11:39 ` Lars Ingebrigtsen
2017-02-16 3:38 ` bug#25710: Branch completion on vc-retrive-tag Artem Malyshev
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='CADwFkmmi9YTAxPEE725iPmSyZ4RUC=g7AJ4yX7W8+841_YTFZw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=25710@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=tom@tromey.com \
/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.