{"thread":{"id":"19253","subject":"can we allow -t abbreviation for --track in 'git branch'","startedAt":"2009-05-09T08:50:07Z","lastAt":"2009-05-10T04:23:27Z","messageCount":4,"participants":["Sitaram Chamarty","Nicolas Sebrecht","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"113395","messageId":"slrnh0agtv.4rv.sitaramc@sitaramc.homelinux.net","threadId":"19253","inReplyTo":null,"subject":"can we allow -t abbreviation for --track in 'git branch'","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-05-09T08:50:07Z","receivedAt":"2009-05-09T08:50:07Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Hello,\n\nWould it make sense to teach \"git branch\" the short option\n\"-t\" the same way that \"git checkout\" knows it, (ie., as an\nabbreviation for \"--track\")?\n\nI use both frequently, and often forget that in \"git branch\"\nthe short option does not work.\n\nIf people think it's OK I'll submit a patch (code and doc).\n\nRegards,\n\nSitaram\n"},{"id":"113396","messageId":"20090509091734.GA12926@vidovic","threadId":"19253","inReplyTo":"slrnh0agtv.4rv.sitaramc@sitaramc.homelinux.net","subject":"Re: can we allow -t abbreviation for --track in 'git branch'","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2009-05-09T09:17:34Z","receivedAt":"2009-05-09T09:17:34Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 09/05/09, Sitaram Chamarty wrote:\n> Hello,\n> \n> Would it make sense to teach \"git branch\" the short option\n> \"-t\" the same way that \"git checkout\" knows it, (ie., as an\n> abbreviation for \"--track\")?\n\nIt makes sense for me.\n\n> I use both frequently, and often forget that in \"git branch\"\n> the short option does not work.\n\nSame here. :-)\n\n\n-- \nNicolas Sebrecht\n"},{"id":"113400","messageId":"7vab5m9ujb.fsf@alter.siamese.dyndns.org","threadId":"19253","inReplyTo":"slrnh0agtv.4rv.sitaramc@sitaramc.homelinux.net","subject":"Re: can we allow -t abbreviation for --track in 'git branch'","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-05-09T15:15:52Z","receivedAt":"2009-05-09T15:15:52Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sitaram Chamarty <sitaramc@gmail.com> writes:\n\n> Would it make sense to teach \"git branch\" the short option\n> \"-t\" the same way that \"git checkout\" knows it, (ie., as an\n> abbreviation for \"--track\")?\n>\n> I use both frequently, and often forget that in \"git branch\"\n> the short option does not work.\n>\n> If people think it's OK I'll submit a patch (code and doc).\n\nI have <20090428152119.GA18935@atc.tcs.com> (aka $gmane/117790) in my\ninbox.\n"},{"id":"113443","messageId":"slrnh0cllu.juu.sitaramc@sitaramc.homelinux.net","threadId":"19253","inReplyTo":"7vab5m9ujb.fsf@alter.siamese.dyndns.org","subject":"Re: can we allow -t abbreviation for --track in 'git branch'","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2009-05-10T04:23:27Z","receivedAt":"2009-05-10T04:23:27Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On 2009-05-09, Junio C Hamano <gitster@pobox.com> wrote:\n> Sitaram Chamarty <sitaramc@gmail.com> writes:\n>\n>> Would it make sense to teach \"git branch\" the short option\n>> \"-t\" the same way that \"git checkout\" knows it, (ie., as an\n>> abbreviation for \"--track\")?\n>>\n>> I use both frequently, and often forget that in \"git branch\"\n>> the short option does not work.\n>>\n>> If people think it's OK I'll submit a patch (code and doc).\n>\n> I have <20090428152119.GA18935@atc.tcs.com> (aka $gmane/117790) in my\n> inbox.\n\nThanks.  I posted it some days ago, but then began to wonder\nif there was more to that change than I thought, and perhaps\nI should have *asked* first.\n\nSitaram\n\nPS: And I saw http://gitster.livejournal.com/33638.html only\njust now... :-)\n"}]}