From: Junio C Hamano <gitster@pobox.com>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH] Improve bash prompt to detect merge / rebase in progress
Date: Sat, 01 Sep 2007 11:07:25 -0700 [thread overview]
Message-ID: <7vir6us1ia.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <11886421573285-git-send-email-robin.rosenberg@dewire.com> (Robin Rosenberg's message of "Sat, 1 Sep 2007 12:22:37 +0200")
Robin Rosenberg <robin.rosenberg@dewire.com> writes:
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index 5ed1821..1fef857 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -64,12 +64,34 @@ __gitdir ()
>
> __git_ps1 ()
> {
> - local b="$(git symbolic-ref HEAD 2>/dev/null)"
> - if [ -n "$b" ]; then
> + local g="$(git rev-parse --git-dir 2>/dev/null)"
> + if [ -n "$g" ]; then
> + local r
> + local b
> + if [ -d "$g/../.dotest" ]
> + then
> + local b="$(git symbolic-ref HEAD 2>/dev/null)"
> + r="|REBASEING"
I might be in the middle of resolving a conflicted "git am".
But I love the idea. We need to think about cleaning up our
"state machine" mechanism to make this kind of thing easier to
do. We've had a few suggestions on the list in the past but
they never passed the suggestion/speculation stage.
next prev parent reply other threads:[~2007-09-01 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 10:22 [PATCH] Improve bash prompt to detect merge / rebase in progress Robin Rosenberg
2007-09-01 18:07 ` Junio C Hamano [this message]
2007-09-01 22:20 ` Shawn O. Pearce
2007-09-02 0:35 ` Johannes Schindelin
2007-09-02 0:44 ` Shawn O. Pearce
2007-09-01 23:02 ` Johannes Schindelin
2007-09-01 23:52 ` Robin Rosenberg
2007-09-02 10:18 ` Johannes Sixt
2007-09-02 10:40 ` Robin Rosenberg
2007-09-04 7:13 ` Shawn O. Pearce
2007-09-30 0:20 ` [PATCH] Improve bash prompt to detect various states like an unfinished merge Robin Rosenberg
2007-10-01 8:15 ` Junio C Hamano
2007-10-01 18:29 ` Robin Rosenberg
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=7vir6us1ia.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
--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).