From: Marc Branchaud <marcnarc@xiplink•com>
To: Peter van der Does <peter@avirtualhome•com>
Cc: "Jonathan Nieder" <jrnieder@gmail•com>,
git@vger•kernel.org, "Shawn O. Pearce" <spearce@spearce•org>,
"SZEDER Gábor" <szeder@ira•uka.de>,
"Brian Gernhardt" <brian@gernhardtsoftware•com>,
"Kevin Ballard" <kevin@sb•org>,
"Mathias Lafeldt" <misfire@debugon•org>
Subject: Re: [completion] Request: Include remote heads as push targets
Date: Fri, 22 Oct 2010 10:50:17 -0400 [thread overview]
Message-ID: <4CC1A4A9.3040703@xiplink.com> (raw)
In-Reply-To: <20101021210842.6545a661@montecarlo.grandprix.int>
On 10-10-21 09:08 PM, Peter van der Does wrote:
>
> In the case of Marc's problem, it would be helpful to see what the
> result is in Bash 3.
Bash v3 seems to work fine:
$ echo $BASH_VERSION
3.2.0(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>
git push origin HEAD:battle<tab><tab>
battle battle.hardened
M.
next prev parent reply other threads:[~2010-10-22 14:50 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
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 [this message]
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=4CC1A4A9.3040703@xiplink.com \
--to=marcnarc@xiplink$(echo .)com \
--cc=brian@gernhardtsoftware$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=kevin@sb$(echo .)org \
--cc=misfire@debugon$(echo .)org \
--cc=peter@avirtualhome$(echo .)com \
--cc=spearce@spearce$(echo .)org \
--cc=szeder@ira$(echo .)uka.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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