git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Improve bash prompt to detect various states like an unfinished merge

From
Robin Rosenberg <robin.rosenberg@dewire.com>
Date
Oct 1, 2007, 18:29 UTC
Message-ID
<200710012029.38100.robin.rosenberg@dewire.com>
In-Reply-To
<7vabr3tfmq.fsf@gitster.siamese.dyndns.org>
måndag 01 oktober 2007 skrev Junio C Hamano:
Show 8 quoted lines
> 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.

You can wonder around different branches while bisecting. The BISECT part is there to remind you that you are already doing bisecting, especially when being away from the prompt for a while. I did some mistakes without it.

> Also if you know you normally get branch name, lack of branch
> name would indicate detached HEAD, I would presume.
Yes, sure, but I like it better this way.
> But other state information may be helpful.

This is an example script, so I'd say it's better to have a little too much and let people remve stuff they don't like in their personal copies.

-- robin
Previous: Junio C Hamano
Message 13 of 13 in “Improve bash prompt to detect merge / rebase in progress”
  1. Improve bash prompt to detect merge / rebase in progressRobin Rosenberg, Sep 1, 2007
  2. Junio C HamanoSep 1, 2007
  3. Shawn O. PearceSep 1, 2007
  4. Johannes SchindelinSep 2, 2007
  5. Shawn O. PearceSep 2, 2007
  6. Johannes SchindelinSep 1, 2007
  7. Robin RosenbergSep 1, 2007
  8. Johannes SixtSep 2, 2007
  9. Robin RosenbergSep 2, 2007
  10. Shawn O. PearceSep 4, 2007
  11. Improve bash prompt to detect various states like an unfinished mergeRobin Rosenberg, Sep 30, 2007
  12. Junio C HamanoOct 1, 2007
  13. Robin RosenbergOct 1, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.