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

Re: any problems with new branch of gitk?

From
A Large Angry SCM <gitzilla@gmail.com>
Date
Mar 5, 2006, 23:16 UTC
Message-ID
<440B7136.2000809@gmail.com>
In-Reply-To
<17419.24973.402408.237865@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
Show 5 quoted lines
> I'm planning to pull the `new' branch of the gitk repository into the
> master branch, making the new version of gitk the standard version
> that will go into the git.git repository.  As far as I know the new
> version does everything the old version does.  Does anyone know of any
> problems with the new gitk that weren't in the old one?

I don't know if the old version has this problem but the new version does not have a "busy" pointer while it's waiting for a merge diff. Take a look at the ACPI mega(octo)pus merge that happened in January.

Previous: Paul MackerrasNext: Alex Riesen
Message 2 of 5 in “any problems with new branch of gitk?”
  1. Paul MackerrasMar 5, 2006
  2. A Large Angry SCMMar 5, 2006
  3. Alex RiesenMar 6, 2006
  4. Paul MackerrasMar 15, 2006
  5. Alex RiesenMar 15, 2006

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.