From: Marc Branchaud <marcnarc@xiplink.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [completion] Request: Include remote heads as push targets
Date: Thu, 21 Oct 2010 12:03:05 -0400 [thread overview]
Message-ID: <4CC06439.8040003@xiplink.com> (raw)
In-Reply-To: <4CC05E4B.1010106@xiplink.com>
On 10-10-21 11:37 AM, Marc Branchaud wrote:
> Hi Shawn,
>
> I find myself wishing that completion would support the following:
>
> git push origin HEAD:<tab>
>
> The options presented at this point should include all the origin/* heads,
> without the "origin/" prefix. Right now (git 1.7.3.1) completion only lets
> me choose from local refs.
Hmmm, perhaps this is really a bug.
When I double-tab, the remote branch name I want is in the list of
possibilities. But when I try to complete by typing a couple of leading
characters then hitting <tab> again, I don't get that name. Instead I get a
tag that starts with the same letters.
More concretely:
$ echo $BASH_VERSION
4.1.5(1)-release
$ git branch -a
bar
baz
* master
remotes/origin/HEAD -> origin/master
remotes/origin/battle
remotes/origin/battle.hardened
remotes/origin/master
$ git tag
bassinet
$ git push origin HEAD:<tab><tab>
battle battle.hardened HEAD master
$ git push origin HEAD:ba<tab><tab>
bar bassinet baz
Wacky!
M.
next prev parent reply other threads:[~2010-10-21 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 15:37 [completion] Request: Include remote heads as push targets Marc Branchaud
2010-10-21 16:03 ` Marc Branchaud [this message]
2010-10-21 19:10 ` Jonathan Nieder
2010-10-22 1:08 ` Peter van der Does
2010-10-22 1:11 ` Kevin Ballard
2010-10-22 14:50 ` Marc Branchaud
2010-10-23 13:04 ` SZEDER Gábor
2010-10-24 0:07 ` Peter van der Does
2010-10-24 11:23 ` SZEDER Gábor
2010-10-24 16:28 ` Peter van der Does
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=4CC06439.8040003@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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.
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 NNTP newsgroup(s).