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
Jun 21, 2009, 14:20 UTC
Message-ID
<2e24e5b90906210720h135b3386t6e7c0a8235fdae57@mail.gmail.com>
In-Reply-To
<7v3a9uszzl.fsf@alter.siamese.dyndns.org>
On Sun, Jun 21, 2009 at 2:52 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 16 quoted lines
>
> Sitaram Chamarty <sitaramc@gmail.com> writes:
>
> > At the command line, this gives you a detailed warning message, but the
> > GUI currently allows it without any fuss.
> >
> > Since the GUI is often used by people much less familiar with git, it
> > seems reasonable to make the GUI more restrictive than the command line,
> > not less.
> > ...
> > This patch helps me a lot.
>
> The patch seems to disable checkout unconditionally, but it at least needs
> an "expert mode" switch to bypass the patch's logic, or (better yet) a
> "training wheel" switch for you to set in repositories of the people you
> manage.
Indeed it does disable checkout of a remote/* branch unconditionally.

I'm not just thinking of people *I* teach when I say that the "training wheel" mode should be the default.

I believe that when someone does this _from the GUI_, it's 100% certain they intended something else. My basis for saying so is (1) even from CLI, it is quite likely, which is why we have a warning, and (2) people who use GUI are often much less expert than people who use CLI.

Actually, what are the odds that someone is expert enough to use a detached HEAD _properly_ (without shooting themselves in the foot), but is _not_ expert enough to just say "git checkout origin/master" at the CLI?  I did not think that combination is worth bothering about.

You're welcome to tell me I'm wrong and that there _are_ such people -- you guys are the gurus here -- but this is what I believe :-)

[Of course, I could just be trying to cover up the fact that those were literally the first 3 lines of Tcl I ever wrote in all my life, and the size and scope of gitk is well beyond my comprehension to do anything non-trivial :-) I'll let you decide which it is, heh!]

Show 9 quoted lines
>
> The above should ideally read:
>
> > diff --git a/gitk b/gitk
> > index 8c66d17..411bc52
> > --- a/gitk
> > +++ b/gitk
>
> if the patch goes to Paulus.
Thanks -- I had not realised that subtlety.

Will make that change and re-send after hearing from either of you about the above.  Because if the decision is that the patch does need to be conditional etc., it'll take me a long while anyway :-(

Regards,
Sitaram
Previous: Junio C HamanoNext: Nanako Shiraishi
Message 4 of 9 in “Please pull gitk master branch”
  1. Paul MackerrasJun 20, 2009
  2. gitk: disable checkout of remote branchSitaram Chamarty, Jun 21, 2009
  3. Junio C HamanoJun 21, 2009
  4. Sitaram ChamartyJun 21, 2009
  5. Nanako ShiraishiJun 21, 2009
  6. Junio C HamanoJun 21, 2009
  7. Sitaram ChamartyJun 22, 2009
  8. gitk: disable checkout of remote branchSitaram Chamarty, Jun 22, 2009
  9. Junio C HamanoJun 21, 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.