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

Re: [PATCH] gitk: disable checkout of remote branch

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Nov 4, 2009, 16:46 UTC
Message-ID
<2e24e5b90911040846y35098a62m2ecd20c54263c494@mail.gmail.com>
In-Reply-To
<1257325697830-3943894.post@n2.nabble.com>
On Wed, Nov 4, 2009 at 2:38 PM, Tim Mazid <timmazid@hotmail.com> wrote:
Show 5 quoted lines
> Hm. I actually meant inside gitk, not git itself. As in, when you click
> inside gitk and try to checkout a remote, it automatically creates a
> tracking branch and checks THAT out instead, whereas command-line git works
> the same way.
> Does that even make sense? :P

It certainly does. And if gitk is internally running the same "checkout" command that may happen automatically (in 1.7 or whatever).

I will "watch this space" as they say :) I stated only my minimum needs (prevent detached HEAD with even less warning [i.e., zero warning] than in CLI) and managed minimum code for it. But any other solution that achives the same effect is also fine!

Previous: Tim MazidNext: Junio C Hamano
Message 9 of 14 in “gitk: disable checkout of remote branch”
  1. gitk: disable checkout of remote branchSitaram Chamarty, Nov 3, 2009
  2. Sverre RabbelierNov 3, 2009
  3. Tim MazidNov 4, 2009
  4. Sitaram ChamartyNov 4, 2009
  5. Tim MazidNov 4, 2009
  6. Sverre RabbelierNov 4, 2009
  7. Jeff KingNov 4, 2009
  8. Tim MazidNov 4, 2009
  9. Sitaram ChamartyNov 4, 2009
  10. Junio C HamanoNov 4, 2009
  11. Jeff KingNov 5, 2009
  12. Junio C HamanoNov 6, 2009
  13. Sverre RabbelierNov 6, 2009
  14. Paul MackerrasNov 14, 2009

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.