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

Re: gitk refresh keeps showing dangling commits

From
Gauthier Östervall <gauthier@ostervall.se>
Date
Dec 4, 2013, 09:45 UTC
Message-ID
<CAM8gEgg2v+isLEcf_rmACBLoaKL0VoA8k=2BpM2JAiY8wNvWuA@mail.gmail.com>
In-Reply-To
<CAByu6UXXVRoQtFkU+A3E885pxVoiPdXXwXbozBP9gciD9BZMBQ@mail.gmail.com>

On Fri, Nov 29, 2013 at 4:27 PM, Thibault Kruse <tibokruse@googlemail.com> wrote:

> and in gitk, I select "Reload"(Ctrl-F5), and I still see both commits,
> not just commit foo.

Do you use the menu entry Reload, or the keyboard shortcut Ctrl+F5? The shortcut was changed a while ago to Shift+F5. http://git.661346.n2.nabble.com/PATCH-gitk-avoid-Meta1-F5-td7444531.html

Previous: Thibault Kruse
Message 2 of 2 in “Re: gitk refresh keeps showing dangling commits”
  1. Thibault KruseNov 29, 2013
  2. Gauthier ÖstervallDec 4, 2013

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.