{"thread":{"id":"47981","subject":"git help clone: questions","startedAt":"2018-03-05T23:15:52Z","lastAt":"2018-03-07T23:34:22Z","messageCount":5,"participants":["kalle","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"341078","messageId":"6ea2b41f-37c3-8540-4763-7688f56fe202@projektwerkstatt.de","threadId":"47981","inReplyTo":null,"subject":"git help clone: questions","fromName":"kalle","fromEmail":"kalle@projektwerkstatt.de","sentAt":"2018-03-05T23:10:01Z","receivedAt":"2018-03-05T23:15:52Z","isPatch":false,"sender":{"key":"kalle@projektwerkstatt.de","avatar":null},"body":"-In the explanation of the option --reference: shouldn't there be\nwritten '' instead of 'reference repository'?\n\ngreetings,\nkalle\n"},{"id":"341088","messageId":"xmqqinaa6l3b.fsf@gitster-ct.c.googlers.com","threadId":"47981","inReplyTo":"6ea2b41f-37c3-8540-4763-7688f56fe202@projektwerkstatt.de","subject":"Re: git help clone: questions","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-03-06T01:36:56Z","receivedAt":"2018-03-06T01:37:03Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"kalle writes:\n\n> -In the explanation of the option --reference: shouldn't there be\n> written '' instead of 'reference repository'?\n\n\"Shouldn't X be Y?\" is not an effective way to communicate; it\nsolicits a \"no, the current one is fine.\" without any explanation.\n\nIf you think X should be Y for some reason, please say \"I think X\nshould be Y BECAUSE Z\" instead. Without stating why you think\ndifferently from what those who wrote the current text, it is hard\nfor people to respond either with \"Yeah, you're right---I agree\nwith Z\" or with \"No, Z does not hold because...\"\n\n"},{"id":"341237","messageId":"81c78c4f-b690-d06c-bb7d-9c65e33777b5@projektwerkstatt.de","threadId":"47981","inReplyTo":"xmqqinaa6l3b.fsf@gitster-ct.c.googlers.com","subject":"Re: git help clone: questions","fromName":"kalle","fromEmail":"kalle@projektwerkstatt.de","sentAt":"2018-03-07T22:30:39Z","receivedAt":"2018-03-07T22:30:49Z","isPatch":false,"sender":{"key":"kalle@projektwerkstatt.de","avatar":null},"body":"I wrote this, because when it is written about 'reference repository', I\nconsider it not totally clear, which repository is meant, as the option\n'--reference ' only names one as .\nFor reasons of clearness, I now propose writing \"reference repository\n\".\n\nkalle\n\nAm 06.03.2018 um 02:36 schrieb Junio C Hamano:\n> kalle writes:\n> \n>> -In the explanation of the option --reference: shouldn't there be\n>> written '' instead of 'reference repository'?\n> \n> \"Shouldn't X be Y?\" is not an effective way to communicate; it\n> solicits a \"no, the current one is fine.\" without any explanation.\n> \n> If you think X should be Y for some reason, please say \"I think X\n> should be Y BECAUSE Z\" instead. Without stating why you think\n> differently from what those who wrote the current text, it is hard\n> for people to respond either with \"Yeah, you're right---I agree\n> with Z\" or with \"No, Z does not hold because...\"\n> \n"},{"id":"341240","messageId":"xmqq4llrzer5.fsf@gitster-ct.c.googlers.com","threadId":"47981","inReplyTo":"81c78c4f-b690-d06c-bb7d-9c65e33777b5@projektwerkstatt.de","subject":"Re: git help clone: questions","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-03-07T22:45:34Z","receivedAt":"2018-03-07T22:45:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"kalle writes:\n\n> Am 06.03.2018 um 02:36 schrieb Junio C Hamano:\n>> kalle writes:\n>> \n>>> -In the explanation of the option --reference: shouldn't there be\n>>> written '' instead of 'reference repository'?\n>> \n>> \"Shouldn't X be Y?\" is not an effective way to communicate; it\n>> solicits a \"no, the current one is fine.\" without any explanation.\n>> \n>> If you think X should be Y for some reason, please say \"I think X\n>> should be Y BECAUSE Z\" instead. Without stating why you think\n>> differently from what those who wrote the current text, it is hard\n>> for people to respond either with \"Yeah, you're right---I agree\n>> with Z\" or with \"No, Z does not hold because...\"\n>> \n> I wrote this, because when it is written about 'reference repository', I\n> consider it not totally clear, which repository is meant, as the option\n> '--reference ' only names one as .\n> For reasons of clearness, I now propose writing \"reference repository\n> \".\n\nI do not have particularly a strong opinion, but I think it is very\nsensible to call the value given to the option \"--reference\" with a\nphrase that is not just \"repository\".\n\nAs the command line of \"clone\" must name one repository (i.e. the\none which we clone from), and its \"--reference\" option must name\nanother repository as its value (i.e. the one that we borrow from in\norder to reduce the object transfer), calling both \nmakes it easier to confuse readers unless the writer carefully makes\nsure that in the desription is unambiguous and it is\nclear which one of these two repositories is being discussed by the\ncontext.\n\nI just re-read the existing Documentation/git-clone.txt and looked\nfor \"reference\". All uses of \"reference repository\" in the prose\nmade sense and I found it would not be an improvement if any of them\nis replaced with just \"repository\". It may be helpful to add\nsomething like:\n\n\t --reference[-if-able] ::\n\t+\tDefine a repository (reference repository) to borrow\n\t+\tobjects from. \n\t\tIf the reference repository is on the local machine,\n\t\t...\n\nto define which repository we mean by that term, though.\n"},{"id":"341248","messageId":"725671ac-0a36-cd9e-c605-6ffdcb7e9a33@projektwerkstatt.de","threadId":"47981","inReplyTo":"xmqq4llrzer5.fsf@gitster-ct.c.googlers.com","subject":"Re: git help clone: questions","fromName":"kalle","fromEmail":"kalle@projektwerkstatt.de","sentAt":"2018-03-07T23:34:14Z","receivedAt":"2018-03-07T23:34:22Z","isPatch":false,"sender":{"key":"kalle@projektwerkstatt.de","avatar":null},"body":"\n\nAm 07.03.2018 um 23:45 schrieb Junio C Hamano:\n> kalle writes:\n> \n>> Am 06.03.2018 um 02:36 schrieb Junio C Hamano:\n>>> kalle writes:\n>>>\n>>>> -In the explanation of the option --reference: shouldn't there be\n>>>> written '' instead of 'reference repository'?\n>>>\n>>> \"Shouldn't X be Y?\" is not an effective way to communicate; it\n>>> solicits a \"no, the current one is fine.\" without any explanation.\n>>>\n>>> If you think X should be Y for some reason, please say \"I think X\n>>> should be Y BECAUSE Z\" instead. Without stating why you think\n>>> differently from what those who wrote the current text, it is hard\n>>> for people to respond either with \"Yeah, you're right---I agree\n>>> with Z\" or with \"No, Z does not hold because...\"\n>>>\n>> I wrote this, because when it is written about 'reference repository', I\n>> consider it not totally clear, which repository is meant, as the option\n>> '--reference ' only names one as .\n>> For reasons of clearness, I now propose writing \"reference repository\n>> \".\n> \n> I do not have particularly a strong opinion, but I think it is very\n> sensible to call the value given to the option \"--reference\" with a\n> phrase that is not just \"repository\".\ni agree and didn't state this. i proposed to add .\n could also be named .\n> \n> As the command line of \"clone\" must name one repository (i.e. the\n> one which we clone from), and its \"--reference\" option must name\n> another repository as its value (i.e. the one that we borrow from in\n> order to reduce the object transfer), calling both \n> makes it easier to confuse readers\n\nyou made my point\n\n unless the writer carefully makes\n> sure that in the desription is unambiguous and it is\n> clear which one of these two repositories is being discussed by the\n> context.>\n> I just re-read the existing Documentation/git-clone.txt and looked\n> for \"reference\". All uses of \"reference repository\" in the prose\n> made sense and I found it would not be an improvement if any of them\n> is replaced with just \"repository\". \n\nThis was never my proposal, though.\n\n It may be helpful to add\n> something like:\n> \n> \t --reference[-if-able] ::\n> \t+\tDefine a repository (reference repository) to borrow\n> \t+\tobjects from. \n> \t\tIf the reference repository is on the local machine,\n> \t\t...\n> \n> to define which repository we mean by that term, though.\n> \n\nin all, it was just meant as a quite small proposal for me. i also don't\nhave any strong opinion about it.\ngreetings,\nkalle\n"}]}