{"thread":{"id":"47982","subject":"user-manual: patch proposals and questions","startedAt":"2018-03-05T23:15:53Z","lastAt":"2018-03-05T23:15:53Z","messageCount":1,"participants":["kalle"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"341079","messageId":"1dff7be2-6406-7727-67ad-3d045b7744ac@projektwerkstatt.de","threadId":"47982","inReplyTo":null,"subject":"user-manual: patch proposals and questions","fromName":"kalle","fromEmail":"kalle@projektwerkstatt.de","sentAt":"2018-03-05T23:08:07Z","receivedAt":"2018-03-05T23:15:53Z","isPatch":false,"sender":{"key":"kalle@projektwerkstatt.de","avatar":null},"body":"The patches are attached.\nFurther some questions:\n\n-see the explanations of the branch command, ca. line 280: wouldn't it\nbe better to use other words than 'references'?\n-sentence \"it shows all commits reachable from the parent commit\": it\nseems wrong to me. The last commit is also shown.\n- chapter \"Browsing revisions\": it seems counterintuitive to me to have\ntwo different logics for the meaning of \"branch1..branch2\" and\n\"branch1...branch2\", according to whether it's the argument of `git log'\nor `git diff'\n-section \"Check whether two branches point at the same history\": 'git\ndiff origin..master' -> shouldn't it be rather 'git diff\nbranch1..branch2'? … or rewrite the example with branch1=origin and\nbranch2=master.\n\ngreetings,\nkalle\n"}]}