unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Tom Tromey <tom@tromey.com>
Cc: 25710@debbugs.gnu.org
Subject: bug#25710: Acknowledgement (25.1.91; vc-retrieve-tag does not offer branch namd completion)
Date: Mon, 20 Feb 2017 00:13:26 +0200	[thread overview]
Message-ID: <ccf1a000-565f-7355-0b34-e933b44b6ba8@yandex.ru> (raw)
In-Reply-To: <87h93txxtm.fsf@tromey.com>

On 17.02.2017 06:09, Tom Tromey wrote:

> That seems fair.

Thanks, installed.

> I still want to add a defcustom to control this.
> For all my cases, the tags would just completely drown out the
> usefulness of this feature.  I don't mind writing that separately.

Will it change how vc-git-revision-completion-table works, across all 
commands? If so, I'm good with it.





  reply	other threads:[~2017-02-19 22:13 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 [this message]
2017-03-04 18:06                   ` Tom Tromey
2017-03-06 11:42                     ` Dmitry Gutov
2020-08-11  7:56                       ` Stefan Kangas
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

  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=ccf1a000-565f-7355-0b34-e933b44b6ba8@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=25710@debbugs.gnu.org \
    --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 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).