From: Sitaram Chamarty <sitaramc@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] gitk: disable checkout of remote branch
Date: Sun, 21 Jun 2009 19:50:29 +0530 [thread overview]
Message-ID: <2e24e5b90906210720h135b3386t6e7c0a8235fdae57@mail.gmail.com> (raw)
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:
>
> 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!]
>
> 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
next prev parent reply other threads:[~2009-06-21 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 6:48 Please pull gitk master branch Paul Mackerras
2009-06-21 9:11 ` [PATCH] gitk: disable checkout of remote branch Sitaram Chamarty
2009-06-21 9:22 ` Junio C Hamano
2009-06-21 14:20 ` Sitaram Chamarty [this message]
2009-06-21 21:34 ` Nanako Shiraishi
2009-06-21 23:27 ` Junio C Hamano
2009-06-22 1:59 ` Sitaram Chamarty
2009-06-22 3:42 ` Sitaram Chamarty
2009-06-21 9:40 ` Please pull gitk master branch Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2009-11-03 16:00 [PATCH] gitk: disable checkout of remote branch Sitaram Chamarty
2009-11-03 16:07 ` Sverre Rabbelier
2009-11-04 0:48 ` Tim Mazid
2009-11-04 1:58 ` Sitaram Chamarty
2009-11-04 6:17 ` Tim Mazid
2009-11-04 6:41 ` Sverre Rabbelier
2009-11-04 7:27 ` Jeff King
2009-11-04 9:08 ` Tim Mazid
2009-11-04 16:46 ` Sitaram Chamarty
2009-11-04 18:03 ` Junio C Hamano
2009-11-05 7:48 ` Jeff King
2009-11-06 0:45 ` Junio C Hamano
2009-11-06 8:30 ` Sverre Rabbelier
2009-11-14 11:14 ` Paul Mackerras
2009-06-05 15:21 preventing checking out remote branch in gitk Sitaram Chamarty
2009-06-06 4:06 ` [PATCH] gitk: disable checkout of remote branch Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e24e5b90906210720h135b3386t6e7c0a8235fdae57@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).