{"thread":{"id":"20521","subject":"A tiny documentation patch","startedAt":"2009-08-10T14:44:19Z","lastAt":"2009-08-12T02:55:22Z","messageCount":4,"participants":["Štěpán Němec","Thomas Rast","Michael J Gruber","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"120158","messageId":"20090810144419.GB24183@headley","threadId":"20521","inReplyTo":null,"subject":"A tiny documentation patch","fromName":"Štěpán Němec","fromEmail":"stepnem@gmail.com","sentAt":"2009-08-10T14:44:19Z","receivedAt":"2009-08-10T14:44:19Z","isPatch":false,"sender":{"key":"stepnem@gmail.com","avatar":"https://avatars.githubusercontent.com/u/106838?v=4"},"body":" Hello,\n\nI noticed a few typos in the git-remote manpage, so I fixed the txt\nsource file and here's the patch.\n\n Best regards and thank you for Git!\n\nŠtěpán Němec\n\n\n>From 65ae3e5cdb241aaaed96a7aeecffb6d305d0b07c Mon Sep 17 00:00:00 2001\nFrom: =?utf-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= \nDate: Mon, 10 Aug 2009 16:29:08 +0200\nSubject: [PATCH] Fix typos in git-remote.txt\n\n---\n Documentation/git-remote.txt | 8 ++++----\n 1 files changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt\nindex 9e2b4ea..0964cee 100644\n--- a/Documentation/git-remote.txt\n+++ b/Documentation/git-remote.txt\n@@ -56,10 +56,10 @@ multiple branches without grabbing all branches.\n With `-m ` option, `$GIT_DIR/remotes//HEAD` is set\n up to point at remote's `` branch. See also the set-head command.\n +\n-In mirror mode, enabled with `\\--mirror`, the refs will not be stored\n+In mirror mode, enabled with `--mirror`, the refs will not be stored\n in the 'refs/remotes/' namespace, but in 'refs/heads/'. This option\n only makes sense in bare repositories. If a remote uses mirror\n-mode, furthermore, `git push` will always behave as if `\\--mirror`\n+mode, furthermore, `git push` will always behave as if `--mirror`\n was passed.\n \n 'rename'::\n@@ -114,14 +114,14 @@ These stale branches have already been removed from the remote repository\n referenced by , but are still locally available in\n \"remotes/\".\n +\n-With `--dry-run` option, report what branches will be pruned, but do no\n+With `--dry-run` option, report what branches will be pruned, but do not\n actually prune them.\n \n 'update'::\n \n Fetch updates for a named set of remotes in the repository as defined by\n remotes.. If a named group is not specified on the command line,\n-the configuration parameter remotes.default will get used; if\n+the configuration parameter remotes.default will be used; if\n remotes.default is not defined, all remotes which do not have the\n configuration parameter remote..skipDefaultUpdate set to true will\n be updated. (See linkgit:git-config[1]).\n-- \n1.6.3.3\n\n"},{"id":"120161","messageId":"200908101659.28291.trast@student.ethz.ch","threadId":"20521","inReplyTo":"20090810144419.GB24183@headley","subject":"Re: A tiny documentation patch","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2009-08-10T14:59:27Z","receivedAt":"2009-08-10T14:59:27Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Štěpán Němec wrote:\n> here's the patch.\n\nPlease read Documentation/SubmittingPatches. In particular, you\nshould send your patch inline (git-send-email can help) and add a\nSigned-off-by.\n\n> I noticed a few typos in the git-remote manpage\n[...]\n> diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt\n[...]\n> -In mirror mode, enabled with `\\--mirror`, the refs will not be stored\n> +In mirror mode, enabled with `--mirror`, the refs will not be stored\n[...]\n> -mode, furthermore, `git push` will always behave as if `\\--mirror`\n> +mode, furthermore, `git push` will always behave as if `--mirror`\n\nWhile I'm not sure how far back you'd have to go to find an asciidoc\nthat does need this escaping, it's definitely *not* a typo. In some\ninstances, -- turns into em dashes.\n\nIf you are seeing stray backslashes in the output (I don't), I suspect\nyou are either running asciidoc 8.x but forgot to set ASCIIDOC8, or\n8.4.1+ and are missing the patch 71c020c (Disable asciidoc 8.4.1+\nsemantics for `{plus}` and friends, 2009-07-25).\n\n> -With `--dry-run` option, report what branches will be pruned, but do no\n> +With `--dry-run` option, report what branches will be pruned, but do not\n> actually prune them.\n\nOk.\n\n> remotes.. If a named group is not specified on the command line,\n> -the configuration parameter remotes.default will get used; if\n> +the configuration parameter remotes.default will be used; if\n\nOk.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"120239","messageId":"4A812575.50105@drmicha.warpmail.net","threadId":"20521","inReplyTo":"200908101659.28291.trast@student.ethz.ch","subject":"Re: A tiny documentation patch","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-08-11T08:01:57Z","receivedAt":"2009-08-11T08:01:57Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Thomas Rast venit, vidit, dixit 10.08.2009 16:59:\n> Štěpán Němec wrote:\n[...]\n> [...]\n>> -In mirror mode, enabled with `\\--mirror`, the refs will not be stored\n>> +In mirror mode, enabled with `--mirror`, the refs will not be stored\n> [...]\n>> -mode, furthermore, `git push` will always behave as if `\\--mirror`\n>> +mode, furthermore, `git push` will always behave as if `--mirror`\n> \n> While I'm not sure how far back you'd have to go to find an asciidoc\n> that does need this escaping, it's definitely *not* a typo. In some\n> instances, -- turns into em dashes.\n> \n> If you are seeing stray backslashes in the output (I don't), I suspect\n> you are either running asciidoc 8.x but forgot to set ASCIIDOC8, or\n> 8.4.1+ and are missing the patch 71c020c (Disable asciidoc 8.4.1+\n> semantics for `{plus}` and friends, 2009-07-25).\n[...]\n\nIn current next's Documentation/, we have 149 lines with `-- and 48\nlines with `\\--. How is our policy regarding old AsciiDoc? I suggest\n(read: volunteer) making these things uniform one way or the other,\ndepending which versions we want to support.\n\nMichael\n"},{"id":"120356","messageId":"7v1vnhbv1h.fsf@alter.siamese.dyndns.org","threadId":"20521","inReplyTo":"4A812575.50105@drmicha.warpmail.net","subject":"Re: A tiny documentation patch","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-08-12T02:55:22Z","receivedAt":"2009-08-12T02:55:22Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Michael J Gruber writes:\n\n> In current next's Documentation/, we have 149 lines with `-- and 48\n> lines with `\\--. How is our policy regarding old AsciiDoc?\n\nWe could drop support for AsciiDoc 7 after all mainstream distros stop\nshipping it. If the need to bend backwards in order to support it gets\ntoo much for us, we might be tempted to drop it sooner, but are we getting\nto that point? I hope not.\n\n> (read: volunteer) making these things uniform one way or the other,\n> depending which versions we want to support.\n\nThanks. 150 does not sound too bad to classify between ones that should\nbe em-dash and that should be double dashes.\n"}]}