{"thread":{"id":"52601","subject":"How log log a feaure request","startedAt":"2020-01-09T02:06:52Z","lastAt":"2020-03-28T11:39:02Z","messageCount":3,"participants":["Tymek Majewski","Junio C Hamano","Philip Oakley"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"389515","messageId":"l0W9VY7TaoqT51RecilbNNTaX35RiCNlJtZKcz04cyKexuG06-bZMlwfor5kCvnIHRRWE7s8TSJLwvA-w4-1poMV_gle8iOzd3-wzFVDUh0=@pm.me","threadId":"52601","inReplyTo":null,"subject":"How log log a feaure request","fromName":"Tymek Majewski","fromEmail":"tmaj@pm.me","sentAt":"2020-01-09T02:06:41Z","receivedAt":"2020-01-09T02:06:52Z","isPatch":false,"sender":{"key":"tmaj@pm.me","avatar":null},"body":"Hello gurus!\n\nI looked at https://git-scm.com/community but I failed to find a place to send feature requests to.\n\nQ: How to submit a feature request (rather than a bug)?\n\n----\n\nWhat is the feature request?\n\nChange git checkout's\n\"Your branch is up to date with 'origin/branch_name_here'\"\n(and similar messages)\nto\n\"Your branch is up to date with the *local* branch 'origin/branch_name_here'\"\n\nReasoning:\n\nI believe that if the git checkout message\n\"Your branch is up to date with 'origin/branch_name_here'\"\nwas\n\"Your branch is up to date with the *local* branch 'origin/branch_name_here'\"\nit would make it clearer to new users what is happening.\n\n\nCheers\nTymek\n"},{"id":"389518","messageId":"xmqq1rs91bo2.fsf@gitster-ct.c.googlers.com","threadId":"52601","inReplyTo":"l0W9VY7TaoqT51RecilbNNTaX35RiCNlJtZKcz04cyKexuG06-bZMlwfor5kCvnIHRRWE7s8TSJLwvA-w4-1poMV_gle8iOzd3-wzFVDUh0=@pm.me","subject":"Re: How log log a feaure request","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-01-09T04:44:29Z","receivedAt":"2020-01-09T04:44:36Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Tymek Majewski <tmaj@pm.me> writes:\n\n> Hello gurus!\n>\n> I looked at https://git-scm.com/community but I failed to find a\n> place to send feature requests to.\n>\n> Q: How to submit a feature request (rather than a bug)?\n\nSending it here, which you did, is how ;-)\n\n> Reasoning:\n>\n> I believe that if the git checkout message\n> \"Your branch is up to date with 'origin/branch_name_here'\"\n> was\n> \"Your branch is up to date with the *local* branch 'origin/branch_name_here'\"\n> it would make it clearer to new users what is happening.\n\nI would be sympathetic to the above, if you did not say \"local\" and\ninstead say \"remote-tracking\".  A local branch is what you can check\nout and grow its history by making a commit while it is checked out.\nThose refs that are updated when you fetch and/or pull from the\nremote repository in order to keep track of the branches they have\nare called remote-tracking branches.\n\nBecause this message is something people see every day when they run\n\"git checkout\", I am not sure if the extra explanation is warranted\nor merely annoying, as \"origin/branch\" notation is used sufficiently\noften for the users to grow accustomed to seeing it and knowing what\nit is, and after all no user will stay to be a newbie forever.\n\nAnother reason why I am somewhat hesitant to endorse the rephrasing\nis because the name of a remote-tracking branch in the real life\ntends to be longer than just 'origin/master'.  We must keep the\nmessage that comes before the name of the remote-tracking branch\nshort in order to make it easier to read the message for the users.\n\nSo... I dunno.\n"},{"id":"394219","messageId":"230b4b11-d1fe-713c-c7b3-c806bff0376f@iee.email","threadId":"52601","inReplyTo":"xmqq1rs91bo2.fsf@gitster-ct.c.googlers.com","subject":"Re: How log log a feaure request","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.email","sentAt":"2020-03-28T11:38:58Z","receivedAt":"2020-03-28T11:39:02Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"Hi Tymek, Junio\n\nOn 09/01/2020 04:44, Junio C Hamano wrote:\n> Tymek Majewski <tmaj@pm.me> writes:\n>\n>> Hello gurus!\n>>\n>> I looked at https://git-scm.com/community but I failed to find a\n>> place to send feature requests to.\n>>\n>> Q: How to submit a feature request (rather than a bug)?\n> Sending it here, which you did, is how ;-)\n>\n>> Reasoning:\n>>\n>> I believe that if the git checkout message\n>> \"Your branch is up to date with 'origin/branch_name_here'\"\n>> was\n>> \"Your branch is up to date with the *local* branch 'origin/branch_name_here'\"\n>> it would make it clearer to new users what is happening.\n> I would be sympathetic to the above, if you did not say \"local\" and\n> instead say \"remote-tracking\". \nCan I agree to both aspects? Yes, the git terminology is \"remote\ntracking branch\", but also that the term is very confusing because it is\nnot actually remote. It is held on the local machine, may not be up to\ndate, and doesn't check.\n\n>  A local branch is what you can check\n> out and grow its history by making a commit while it is checked out.\n> Those refs that are updated when you fetch and/or pull from the\n> remote repository in order to keep track of the branches they have\n> are called remote-tracking branches.\nIf we need to explain this then perhaps we haven't been good at naming.\nIt took me a very long while to appreciate it was all backwards as its a\n(local) branch that tracks a remote [sort of reverse Polish notation, or\nFrench 'de' notation (OTAN/NATO)].\n\n>\n> Because this message is something people see every day when they run\n> \"git checkout\", I am not sure if the extra explanation is warranted\n> or merely annoying, as \"origin/branch\" notation is used sufficiently\n> often for the users to grow accustomed \nI think we have a 'continue to be confused' possibility here.\n\n> to seeing it and knowing what\n> it is, and after all no user will stay to be a newbie forever.\nI'm sure that for all those who have worked with Git from early days are\nquite happy with the rtb notation (it was learnt as it developed), but I\nfeel that newer users who have arrived from always-on central-server\nenvironments are having multiple challenges all arriving at same time,\nso aren't learning.\n> Another reason why I am somewhat hesitant to endorse the rephrasing\n> is because the name of a remote-tracking branch in the real life\n> tends to be longer than just 'origin/master'.  \n\n> We must keep the\n> message that comes before the name of the remote-tracking branch\n> short in order to make it easier to read the message for the users.\nTrue. Perhaps move the \"Your\" from the beginning of the sentence, to the\nend?\n\n\"Branch is up to date with your 'origin/branch_name_here'\" or\n\"This branch is up to date with your 'origin/branch_name_here'\"\n\n>\n> So... I dunno.\n--\nPhilip\n(still catching up with the list)\n"}]}