{"thread":{"id":"21463","subject":"[PATCH] gitk: disable checkout of remote branch","startedAt":"2009-11-03T16:00:12Z","lastAt":"2009-11-14T11:14:03Z","messageCount":14,"participants":["Sitaram Chamarty","Sverre Rabbelier","Tim Mazid","Jeff King","Junio C Hamano","Paul Mackerras"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"126654","messageId":"2e24e5b90911030800j22b00372r99a56c3f847a3644@mail.gmail.com","threadId":"21463","inReplyTo":null,"subject":"[PATCH] gitk: disable checkout of remote branch","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-11-03T16:00:12Z","receivedAt":"2009-11-03T16:00:12Z","isPatch":true,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"At the command line, this gives you a detailed warning message, but the\nGUI currently allows it without any fuss.\n\nSince the GUI is often used by people much less familiar with git, it\nseems reasonable to make the GUI more restrictive than the command line,\nnot less.\n\nThis prevents a lot of detached HEAD commits by new users.\n\nSigned-off-by: Sitaram Chamarty \n---\n gitk | 3 +++\n 1 files changed, 3 insertions(+), 0 deletions(-)\n\ndiff --git a/gitk b/gitk\nindex db5ec54..95e27d4 100755\n--- a/gitk\n+++ b/gitk\n@@ -8897,6 +8897,9 @@ proc headmenu {x y id head} {\n set headmenuid $id\n set headmenuhead $head\n set state normal\n+ if {[string match \"remotes/*\" $head]} {\n+\tset state disabled\n+ }\n if {$head eq $mainhead} {\n \tset state disabled\n }\n-- \n1.6.5\n"},{"id":"126655","messageId":"fabb9a1e0911030807h6b76b661pef75628a1255356@mail.gmail.com","threadId":"21463","inReplyTo":"2e24e5b90911030800j22b00372r99a56c3f847a3644@mail.gmail.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-11-03T16:07:28Z","receivedAt":"2009-11-03T16:07:28Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Tue, Nov 3, 2009 at 17:00, Sitaram Chamarty wrote:\n> At the command line, this gives you a detailed warning message, but the\n> GUI currently allows it without any fuss.\n\nThis is even better than an annoying popup dialog, as we all know\nthose are just ignored anyway :).\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"126693","messageId":"1257295737457-3942366.post@n2.nabble.com","threadId":"21463","inReplyTo":"fabb9a1e0911030807h6b76b661pef75628a1255356@mail.gmail.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Tim Mazid","fromEmail":"timmazid@hotmail.com","sentAt":"2009-11-04T00:48:57Z","receivedAt":"2009-11-04T00:48:57Z","isPatch":true,"sender":{"key":"timmazid@hotmail.com","avatar":null},"body":"\n\nSverre Rabbelier-2 wrote:\n> \n> On Tue, Nov 3, 2009 at 17:00, Sitaram Chamarty wrote:\n>> At the command line, this gives you a detailed warning message, but the\n>> GUI currently allows it without any fuss.\n> \n> This is even better than an annoying popup dialog, as we all know\n> those are just ignored anyway :).\n> \n\nMight be better to include a configuration option to allow this, for those\nthat know what they're doing. Most of the people that know what they're\ndoing will use the command line, anyway, but it may irritate some people.\n-- \nView this message in context: http://n2.nabble.com/PATCH-gitk-disable-checkout-of-remote-branch-tp3939363p3942366.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"126701","messageId":"2e24e5b90911031758t651735f9xe9d078079112cfa6@mail.gmail.com","threadId":"21463","inReplyTo":"1257295737457-3942366.post@n2.nabble.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-11-04T01:58:54Z","receivedAt":"2009-11-04T01:58:54Z","isPatch":true,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Wed, Nov 4, 2009 at 6:18 AM, Tim Mazid wrote:\n\n> Might be better to include a configuration option to allow this, for those\n> that know what they're doing. Most of the people that know what they're\n> doing will use the command line, anyway, but it may irritate some people.\n\nI considered that but found my tcl fu was seriously lacking. These\nare literally the first 3 lines of tcl I ever wrote in my life, and\nthis program is one huge 11,000+ line monolith, so I'm naturally\nscared to make more than very, very, small changes :)\n\nIn any case, as you said, most people who know what they're doing can\nuse the CLI to get there anyway...\n"},{"id":"126721","messageId":"1257315478920-3943388.post@n2.nabble.com","threadId":"21463","inReplyTo":"2e24e5b90911031758t651735f9xe9d078079112cfa6@mail.gmail.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Tim Mazid","fromEmail":"timmazid@hotmail.com","sentAt":"2009-11-04T06:17:58Z","receivedAt":"2009-11-04T06:17:58Z","isPatch":true,"sender":{"key":"timmazid@hotmail.com","avatar":null},"body":"\n\nSitaram Chamarty wrote:\n> \n> On Wed, Nov 4, 2009 at 6:18 AM, Tim Mazid wrote:\n> \n>> Might be better to include a configuration option to allow this, for\n>> those\n>> that know what they're doing. Most of the people that know what they're\n>> doing will use the command line, anyway, but it may irritate some people.\n> \n> I considered that but found my tcl fu was seriously lacking. These\n> are literally the first 3 lines of tcl I ever wrote in my life, and\n> this program is one huge 11,000+ line monolith, so I'm naturally\n> scared to make more than very, very, small changes :)\n> \n> In any case, as you said, most people who know what they're doing can\n> use the CLI to get there anyway...\n> \n\nHm, now that I think about it, what might be better is to just do what\nshould be done for them. :P\n\nSo instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout -b\nBRANCH REMOTE/BRANCH'.\n\nI know you said, you don't know, tcl, but just throwing it out there for\nanyone else.\n\nCheers,\nTim.\n-- \nView this message in context: http://n2.nabble.com/PATCH-gitk-disable-checkout-of-remote-branch-tp3939363p3943388.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"126724","messageId":"fabb9a1e0911032241u3735fa30heaa195d959879f5a@mail.gmail.com","threadId":"21463","inReplyTo":"1257315478920-3943388.post@n2.nabble.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-11-04T06:41:28Z","receivedAt":"2009-11-04T06:41:28Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Wed, Nov 4, 2009 at 07:17, Tim Mazid wrote:\n> So instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout -b\n> BRANCH REMOTE/BRANCH'.\n\nAutomagically doing 'git checkout -t remote/branch' when asked to do\n'git checkout remote/branch' was suggested earlier on the list and I\nthink there was even a patch that implemented it, not sure what the\noutcome of the series was. I do remember that Peff was annoyed by it\nat the GitTogether though so it might be a bad idea.\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"126732","messageId":"20091104072709.GC24263@coredump.intra.peff.net","threadId":"21463","inReplyTo":"fabb9a1e0911032241u3735fa30heaa195d959879f5a@mail.gmail.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-11-04T07:27:09Z","receivedAt":"2009-11-04T07:27:09Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Nov 04, 2009 at 07:41:28AM +0100, Sverre Rabbelier wrote:\n\n> On Wed, Nov 4, 2009 at 07:17, Tim Mazid wrote:\n> > So instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout -b\n> > BRANCH REMOTE/BRANCH'.\n> \n> Automagically doing 'git checkout -t remote/branch' when asked to do\n> 'git checkout remote/branch' was suggested earlier on the list and I\n> think there was even a patch that implemented it, not sure what the\n> outcome of the series was. I do remember that Peff was annoyed by it\n> at the GitTogether though so it might be a bad idea.\n\nIt's in 'next' now. And for the record, my complaint about its behavior\nturned out to be partially because I was an idiot. I am still not\nconvinced that we won't later regret leaving the stale local branch\nsitting around, or that users won't find it confusing to see:\n\n $ git checkout foo\n Branch foo set up to track remote branch foo from origin.\n Switched to a new branch 'foo'\n\n ... time passes ...\n\n $ git checkout foo\n Switched to branch 'foo'\n Your branch is behind 'origin/foo' by 1 commit, and can be fast-forwarded.\n\n(i.e., you do the same thing, but get two very different results, and\nyou have to know how to do the fast-forward. Trivial if you are used to\nworking with branches, but perhaps not if you are just sightseeing).\n\nBut I am no longer planning on writing a long-winded rant about the\nfeature. ;)\n\n-Peff\n"},{"id":"126745","messageId":"1257325697830-3943894.post@n2.nabble.com","threadId":"21463","inReplyTo":"20091104072709.GC24263@coredump.intra.peff.net","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Tim Mazid","fromEmail":"timmazid@hotmail.com","sentAt":"2009-11-04T09:08:17Z","receivedAt":"2009-11-04T09:08:17Z","isPatch":true,"sender":{"key":"timmazid@hotmail.com","avatar":null},"body":"\n\n\nJeff King wrote:\n> \n> On Wed, Nov 04, 2009 at 07:41:28AM +0100, Sverre Rabbelier wrote:\n> \n>> On Wed, Nov 4, 2009 at 07:17, Tim Mazid wrote:\n>> > So instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout\n>> -b\n>> > BRANCH REMOTE/BRANCH'.\n>> \n>> Automagically doing 'git checkout -t remote/branch' when asked to do\n>> 'git checkout remote/branch' was suggested earlier on the list and I\n>> think there was even a patch that implemented it, not sure what the\n>> outcome of the series was. I do remember that Peff was annoyed by it\n>> at the GitTogether though so it might be a bad idea.\n> \n> It's in 'next' now. And for the record, my complaint about its behavior\n> turned out to be partially because I was an idiot. I am still not\n> convinced that we won't later regret leaving the stale local branch\n> sitting around, or that users won't find it confusing to see:\n> \n> $ git checkout foo\n> Branch foo set up to track remote branch foo from origin.\n> Switched to a new branch 'foo'\n> \n> ... time passes ...\n> \n> $ git checkout foo\n> Switched to branch 'foo'\n> Your branch is behind 'origin/foo' by 1 commit, and can be\n> fast-forwarded.\n> \n\nHm. I actually meant inside gitk, not git itself. As in, when you click\ninside gitk and try to checkout a remote, it automatically creates a\ntracking branch and checks THAT out instead, whereas command-line git works\nthe same way.\nDoes that even make sense? :P\n-- \nView this message in context: http://n2.nabble.com/PATCH-gitk-disable-checkout-of-remote-branch-tp3939363p3943894.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"126775","messageId":"2e24e5b90911040846y35098a62m2ecd20c54263c494@mail.gmail.com","threadId":"21463","inReplyTo":"1257325697830-3943894.post@n2.nabble.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-11-04T16:46:04Z","receivedAt":"2009-11-04T16:46:04Z","isPatch":true,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Wed, Nov 4, 2009 at 2:38 PM, Tim Mazid wrote:\n\n> Hm. I actually meant inside gitk, not git itself. As in, when you click\n> inside gitk and try to checkout a remote, it automatically creates a\n> tracking branch and checks THAT out instead, whereas command-line git works\n> the same way.\n> Does that even make sense? :P\n\nIt certainly does. And if gitk is internally running the same\n\"checkout\" command that may happen automatically (in 1.7 or whatever).\n\nI will \"watch this space\" as they say :) I stated only my minimum\nneeds (prevent detached HEAD with even less warning [i.e., zero\nwarning] than in CLI) and managed minimum code for it. But any other\nsolution that achives the same effect is also fine!\n"},{"id":"126782","messageId":"7vhbtai2uy.fsf@alter.siamese.dyndns.org","threadId":"21463","inReplyTo":"20091104072709.GC24263@coredump.intra.peff.net","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-11-04T18:03:49Z","receivedAt":"2009-11-04T18:03:49Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> On Wed, Nov 04, 2009 at 07:41:28AM +0100, Sverre Rabbelier wrote:\n>\n>> On Wed, Nov 4, 2009 at 07:17, Tim Mazid wrote:\n>> > So instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout -b\n>> > BRANCH REMOTE/BRANCH'.\n>> \n>> Automagically doing 'git checkout -t remote/branch' when asked to do\n>> 'git checkout remote/branch' was suggested earlier on the list and I\n>> think there was even a patch that implemented it, not sure what the\n>> outcome of the series was. I do remember that Peff was annoyed by it\n>> at the GitTogether though so it might be a bad idea.\n>\n> It's in 'next' now.\n\nIsn't it quite different? What's in 'next' for 1.7.0 is to guess the\nuser's intention when:\n\n - he says 'git checkout BRANCH'; and\n\n - BRANCH does not yet exist; and\n\n - BRANCH does not name a commit so the request cannot be to detach HEAD\n at some commit (like REMOTE/BRANCH); and\n\n - there is a unique REMOTE that has BRANCH. \n\nThe user wants to check out his own BRANCH (the request lacks REMOTE to\nstart with) but such a branch does not exist yet, and there is only one\nsensible commit to start that new branch, hence we DWIM it and helpfully\nrun \"git branch -t BRANCH REMOTE/BRANCH\" automatically before performing\n\"git checkout BRANCH\" that was asked.\n\nWe never claim to allow checking out the remote tracking branch itself.\nThe new guessing is only about a local branch that does not exist yet.\n\n> ... I am still not convinced that we won't later regret leaving the\n> stale local branch sitting around, or that users won't find it confusing\n> to see:\n>\n> $ git checkout foo\n> Branch foo set up to track remote branch foo from origin.\n> Switched to a new branch 'foo'\n>\n> ... time passes ...\n>\n> $ git checkout foo\n> Switched to branch 'foo'\n> Your branch is behind 'origin/foo' by 1 commit, and can be fast-forwarded.\n>\n> (i.e., you do the same thing, but get two very different results,...\n\nI think this is primarily because the way this DWIM is totally silent in\nthe transcript is misleading. If you explain it the way I outlined above,\nI do not think there is any confusion. That is, there is no way for the\nuser to get confused if the command sequence were like so:\n\n $ git branch -t foo origin/foo\n Branch foo set up to track remote branch foo from origin.\n $ git checkout foo\n Switched to a new branch 'foo'\n\n ... time passes ...\n\n $ git checkout foo\n Switched to branch 'foo'\n Your branch is behind 'origin/foo' by 1 commit, and can be fast-forwarded.\n\nIt could just be a matter of telling what we are doing a bit more\nexplicitly when this DWIM kicks in. How about this?\n\n $ git checkout foo\n (first forking your own 'foo' from 'origin/foo')\n Branch foo set up to track remote branch foo from origin.\n Switched to a new branch 'foo'\n\nIn any case, I do not think the DWIM would kick in when you try to detach\nat remote branch head. I did not check gitk code to find out the exact\ncommand line it uses, but I do not think it runs \"checkout BRANCH\". The\ncommand needs to be at least \"checkout REMOTE/BRANCH\" to work the way it\ndoes now with any released version of git, and I would not be surprised if\npaulus was cautious enough to have spelled it as \"refs/REMOTE/BRANCH\" to\navoid any potential ambiguity issues.\n"},{"id":"126885","messageId":"20091105074808.GA12114@coredump.intra.peff.net","threadId":"21463","inReplyTo":"7vhbtai2uy.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-11-05T07:48:08Z","receivedAt":"2009-11-05T07:48:08Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Nov 04, 2009 at 10:03:49AM -0800, Junio C Hamano wrote:\n\n> Jeff King writes:\n> \n> > On Wed, Nov 04, 2009 at 07:41:28AM +0100, Sverre Rabbelier wrote:\n> >\n> >> On Wed, Nov 4, 2009 at 07:17, Tim Mazid wrote:\n> >> > So instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout -b\n> >> > BRANCH REMOTE/BRANCH'.\n> >> \n> >> Automagically doing 'git checkout -t remote/branch' when asked to do\n> >> 'git checkout remote/branch' was suggested earlier on the list and I\n> >> think there was even a patch that implemented it, not sure what the\n> >> outcome of the series was. I do remember that Peff was annoyed by it\n> >> at the GitTogether though so it might be a bad idea.\n> >\n> > It's in 'next' now.\n> \n> Isn't it quite different? What's in 'next' for 1.7.0 is to guess the\n> user's intention when:\n\nSorry, yes, I just saw Sverre's comment and misread the original\nproposal. Checking out \"$remote/$branch\" will still detach the HEAD,\nand I don't think anybody has a previous proposal to change that.\n\n> I think this is primarily because the way this DWIM is totally silent in\n> the transcript is misleading. If you explain it the way I outlined above,\n> I do not think there is any confusion. That is, there is no way for the\n> user to get confused if the command sequence were like so:\n> \n> $ git branch -t foo origin/foo\n> Branch foo set up to track remote branch foo from origin.\n> $ git checkout foo\n> Switched to a new branch 'foo'\n> \n> ... time passes ...\n> \n> $ git checkout foo\n> Switched to branch 'foo'\n> Your branch is behind 'origin/foo' by 1 commit, and can be fast-forwarded.\n> \n> It could just be a matter of telling what we are doing a bit more\n> explicitly when this DWIM kicks in. How about this?\n>\n> $ git checkout foo\n> (first forking your own 'foo' from 'origin/foo')\n> Branch foo set up to track remote branch foo from origin.\n> Switched to a new branch 'foo'\n\nThis is much better than the current behavior, IMHO. It at least says\nwhat is going on, so a user who actually reads the message will have a\nchance of knowing what happened.\n\nThe devil's advocate argument is that the difference between the \"branch\n-t\" and the DWIM is that in the former, the user intentionally asks for\na new branch, whereas in the latter, they must realize (by reading and\nunderstanding) that a new branch has been created.\n\nMaybe that difference isn't relevant, and people actually read and\nunderstand everything git says. Maybe not. I dunno. I don't think we\nhave any real data yet on how people will perceive the feature over\ntime, and I suspect the only way to get it is to release with it and see\nwhat happens.\n\n> In any case, I do not think the DWIM would kick in when you try to detach\n> at remote branch head. I did not check gitk code to find out the exact\n> command line it uses, but I do not think it runs \"checkout BRANCH\". The\n> command needs to be at least \"checkout REMOTE/BRANCH\" to work the way it\n> does now with any released version of git, and I would not be surprised if\n> paulus was cautious enough to have spelled it as \"refs/REMOTE/BRANCH\" to\n> avoid any potential ambiguity issues.\n\nYes, I was confused when I wrote the original. I agree that \"checkout\nREMOTE/BRANCH\" from the command line should still detach. If gitk wants\nto prevent people accidentally detaching HEAD, the context menu for\nremote branch boxes should probably detect remote branches and say\nsomething like \"Create local branch 'foo' from 'origin/foo'\".\n\n-Peff\n"},{"id":"126941","messageId":"7v8wek7a6z.fsf@alter.siamese.dyndns.org","threadId":"21463","inReplyTo":"20091105074808.GA12114@coredump.intra.peff.net","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-11-06T00:45:24Z","receivedAt":"2009-11-06T00:45:24Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n>> Isn't it quite different? What's in 'next' for 1.7.0 is to guess the\n>> user's intention when:\n>\n> Sorry, yes, I just saw Sverre's comment and misread the original\n> proposal. Checking out \"$remote/$branch\" will still detach the HEAD,\n> and I don't think anybody has a previous proposal to change that.\n\nHeh, I think both of us forgot that we decided it is safe enough not to\nwait for 1.7.0 already, because the situation this kicks in has always\nresulted in an error. We have it in master since e3de372 (Merge branch\n'jc/checkout-auto-track', 2009-10-30).\n"},{"id":"126962","messageId":"fabb9a1e0911060030u779ddb64x6017e06f44ac2c10@mail.gmail.com","threadId":"21463","inReplyTo":"7v8wek7a6z.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2009-11-06T08:30:08Z","receivedAt":"2009-11-06T08:30:08Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Fri, Nov 6, 2009 at 01:45, Junio C Hamano wrote:\n> Jeff King writes:\n>> Sorry, yes, I just saw Sverre's comment and misread the original\n>> proposal.  Checking out \"$remote/$branch\" will still detach the HEAD,\n>> and I don't think anybody has a previous proposal to change that.\n>\n> Heh, I think both of us forgot that we decided it is safe enough not to\n> wait for 1.7.0 already, because the situation this kicks in has always\n> resulted in an error.  We have it in master since e3de372 (Merge branch\n> 'jc/checkout-auto-track', 2009-10-30).\n\nSorry for causing so much confusion, I misremembered what the patch\nwas about (\"git checkout \" vs \"git checkout\n/\"). Apologies.\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"127542","messageId":"19198.37115.314162.750365@cargo.ozlabs.ibm.com","threadId":"21463","inReplyTo":"2e24e5b90911030800j22b00372r99a56c3f847a3644@mail.gmail.com","subject":"Re: [PATCH] gitk: disable checkout of remote branch","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2009-11-14T11:14:03Z","receivedAt":"2009-11-14T11:14:03Z","isPatch":true,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Sitaram Chamarty writes:\n\n> This prevents a lot of detached HEAD commits by new users.\n> \n> Signed-off-by: Sitaram Chamarty \n\nThanks, applied.\n\nPaul.\n"}]}