{"thread":{"id":"8692","subject":"[PATCH] Escape some tilde characters causing spurious subscripts in documentation","startedAt":"2007-06-23T22:19:15Z","lastAt":"2007-06-23T22:36:36Z","messageCount":2,"participants":["Jason Sewall","Johannes Schindelin"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"45626","messageId":"31e9dd080706231519p25520183vb0f102a4585e17f4@mail.gmail.com","threadId":"8692","inReplyTo":null,"subject":"[PATCH] Escape some tilde characters causing spurious subscripts in documentation","fromName":"Jason Sewall","fromEmail":"jasonsewall@gmail.com","sentAt":"2007-06-23T22:19:15Z","receivedAt":"2007-06-23T22:19:15Z","isPatch":true,"sender":{"key":"jasonsewall@gmail.com","avatar":null},"body":"A few unescaped tilde characters were causing long parts of the html\ndocumentation to be formatted as footnotes. This patch fixes them; I\nthink I found all of them, but no promises.\n\nSigned-off-by: Jason Sewall <jasonsewall@gmail.com>\n---\nThis is my first attempt at actually submitting a patch to the git\nlist; let me know if this is a reasonably presented patch. It is truly\ntrivial, but getting those docs cleaned up is important!\n\n Documentation/git-bundle.txt |    8 ++++----\n Documentation/git-daemon.txt |    2 +-\n 2 files changed, 5 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt\nindex 5051e2b..d89f350 100644\n--- a/Documentation/git-bundle.txt\n+++ b/Documentation/git-bundle.txt\n@@ -61,7 +61,7 @@ unbundle <file>::\n [git-rev-list-args...]::\n        A list of arguments, acceptable to git-rev-parse and\n        git-rev-list, that specify the specific objects and references\n-       to transport.  For example, \"master~10..master\" causes the\n+       to transport.  For example, \"master\\~10..master\" causes the\n        current master reference to be packaged along with all objects\n        added since its 10th ancestor commit.  There is no explicit\n        limit to the number of references and objects that may be\n@@ -80,12 +80,12 @@ SPECIFYING REFERENCES\n\n git-bundle will only package references that are shown by\n git-show-ref: this includes heads, tags, and remote heads.  References\n-such as master~1 cannot be packaged, but are perfectly suitable for\n+such as master\\~1 cannot be packaged, but are perfectly suitable for\n defining the basis.  More than one reference may be packaged, and more\n than one basis can be specified.  The objects packaged are those not\n contained in the union of the given bases.  Each basis can be\n-specified explicitly (e.g., ^master~10), or implicitly (e.g.,\n-master~10..master, master --since=10.days.ago).\n+specified explicitly (e.g., ^master\\~10), or implicitly (e.g.,\n+master\\~10..master, master --since=10.days.ago).\n\n It is very important that the basis used be held by the destination.\n It is okay to err on the side of conservatism, causing the bundle file\ndiff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt\nindex 4b30b18..3f9cec5 100644\n--- a/Documentation/git-daemon.txt\n+++ b/Documentation/git-daemon.txt\n@@ -98,7 +98,7 @@ OPTIONS\n \t--verbose, thus by default only error conditions will be logged.\n\n --user-path, --user-path=path::\n-\tAllow ~user notation to be used in requests.  When\n+\tAllow \\~user notation to be used in requests.  When\n \tspecified with no parameter, requests to\n \tgit://host/~alice/foo is taken as a request to access\n \t'foo' repository in the home directory of user `alice`.\n-- \n1.5.2.1.280.g38570\n"},{"id":"45627","messageId":"Pine.LNX.4.64.0706232333320.4059@racer.site","threadId":"8692","inReplyTo":"31e9dd080706231519p25520183vb0f102a4585e17f4@mail.gmail.com","subject":"Re: [PATCH] Escape some tilde characters causing spurious subscripts in documentation","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-06-23T22:36:36Z","receivedAt":"2007-06-23T22:36:36Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 23 Jun 2007, Jason Sewall wrote:\n\n> This is my first attempt at actually submitting a patch to the git list; \n> let me know if this is a reasonably presented patch. It is truly \n> trivial, but getting those docs cleaned up is important!\n\nYou followed SubmittingPatches really well. Commit message, diffstat and \nthe comment between message and diffstat.\n\nThanks.\n\n> @@ -80,12 +80,12 @@ SPECIFYING REFERENCES\n> \n> git-bundle will only package references that are shown by\n> git-show-ref: this includes heads, tags, and remote heads.  References\n> -such as master~1 cannot be packaged, but are perfectly suitable for\n> +such as master\\~1 cannot be packaged, but are perfectly suitable for\n\nBut you have some whitespace damage, unfortunately. The space at the \nbeginning of the lines is missing.\n\nJudging from your email address, I suspect you copied&pasted the patch \ninto the web interface, and somehow this mangled the white space.\n\nCan you send it somehow via SMTP?\n\nCiao,\nDscho\n"}]}