From: Jay Soffian <jaysoffian@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git branch --current?
Date: Wed, 17 Mar 2010 11:14:44 -0400 [thread overview]
Message-ID: <76718491003170814v71e31e91q994daee849da4caf@mail.gmail.com> (raw)
In-Reply-To: <fcaeb9bf1003170804s4c9fdbb6id2c045bdb90f8c6f@mail.gmail.com>
On Wed, Mar 17, 2010 at 11:04 AM, Nguyen Thai Ngoc Duy
<pclouds@gmail.com> wrote:
> Hmm.. I have alias.pwb = symbolic-ref HEAD. Both solutions are not as
> good as "git branch", say detached HEAD case.
How about naming something like this git-pwb and copying it to
somewhere in PATH:
#!/bin/sh
. /opt/git/share/git-core/git-completion.bash
echo $(__git_ps1)
Perhaps you are inspired to contribute git-completion.csh?
:-)
j.
next prev parent reply other threads:[~2010-03-17 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 14:43 git branch --current? Nguyen Thai Ngoc Duy
2010-03-17 14:48 ` Jay Soffian
2010-03-17 15:04 ` Nguyen Thai Ngoc Duy
2010-03-17 15:14 ` Jay Soffian [this message]
2010-03-17 19:06 ` David Aguilar
2010-03-18 2:00 ` Nguyen Thai Ngoc Duy
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=76718491003170814v71e31e91q994daee849da4caf@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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.
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).