All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: gitster@pobox.com, git@vger.kernel.org, johannes.sixt@telecom.at,
	spearce@spearce.org
Subject: Re: [PATCH] Improve bash prompt to detect various states like an unfinished merge
Date: Mon, 01 Oct 2007 01:15:25 -0700	[thread overview]
Message-ID: <7vabr3tfmq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1191111645134-git-send-email-robin.rosenberg@dewire.com> (Robin Rosenberg's message of "Sun, 30 Sep 2007 02:20:45 +0200")

Robin Rosenberg <robin.rosenberg@dewire.com> writes:

> This patch makes the git prompt (when enabled) show if a merge or a
> rebase is unfinished. It also detects if a bisect is being done as
> well as detached checkouts.

Since you show the name of the branch anyway, I have to wonder
why you should say BISECT.

Also if you know you normally get branch name, lack of branch
name would indicate detached HEAD, I would presume.

But other state information may be helpful.

  reply	other threads:[~2007-10-01  8:15 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
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 [this message]
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=7vabr3tfmq.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.sixt@telecom.at \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.