{"thread":{"id":"35166","subject":"[PATCH] git-svn documentation: Use tabs consistently within the ascii doc","startedAt":"2013-10-18T19:56:10Z","lastAt":"2013-10-21T19:36:06Z","messageCount":3,"participants":["Stefan Beller","Keshav Kini"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"229188","messageId":"1382126170-8907-1-git-send-email-stefanbeller@googlemail.com","threadId":"35166","inReplyTo":null,"subject":"[PATCH] git-svn documentation: Use tabs consistently within the ascii doc","fromName":"Stefan Beller","fromEmail":"stefanbeller@googlemail.com","sentAt":"2013-10-18T19:56:10Z","receivedAt":"2013-10-18T19:56:10Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"While I can understand 4 or 7 white spaces are fancy, we'd rather want\nto use tabs throughout the whole document.\n\nSigned-off-by: Stefan Beller <stefanbeller@googlemail.com>\n---\n Documentation/git-svn.txt | 22 +++++++++++-----------\n 1 file changed, 11 insertions(+), 11 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 2a38476..58578ad 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -175,11 +175,11 @@ Skip \"branches\" and \"tags\" of first level directories;;\n \tprecedence over '--include-paths'.\n \n --log-window-size=<n>;;\n-    Fetch <n> log entries per request when scanning Subversion history.\n-    The default is 100. For very large Subversion repositories, larger\n-    values may be needed for 'clone'/'fetch' to complete in reasonable\n-    time. But overly large values may lead to higher memory usage and\n-    request timeouts.\n+\tFetch <n> log entries per request when scanning Subversion history.\n+\tThe default is 100. For very large Subversion repositories, larger\n+\tvalues may be needed for 'clone'/'fetch' to complete in reasonable\n+\ttime. But overly large values may lead to higher memory usage and\n+\trequest timeouts.\n \n 'clone'::\n \tRuns 'init' and 'fetch'.  It will automatically create a\n@@ -366,12 +366,12 @@ environment). This command has the same behaviour.\n Any other arguments are passed directly to 'git log'\n \n 'blame'::\n-       Show what revision and author last modified each line of a file. The\n-       output of this mode is format-compatible with the output of\n-       `svn blame' by default. Like the SVN blame command,\n-       local uncommitted changes in the working tree are ignored;\n-       the version of the file in the HEAD revision is annotated. Unknown\n-       arguments are passed directly to 'git blame'.\n+\tShow what revision and author last modified each line of a file. The\n+\toutput of this mode is format-compatible with the output of\n+\t`svn blame' by default. Like the SVN blame command,\n+\tlocal uncommitted changes in the working tree are ignored;\n+\tthe version of the file in the HEAD revision is annotated. Unknown\n+\targuments are passed directly to 'git blame'.\n +\n --git-format;;\n \tProduce output in the same format as 'git blame', but with\n-- \n1.8.4.1.511.g52c26ce\n"},{"id":"229202","messageId":"87ob6mxcpb.fsf@gmail.com","threadId":"35166","inReplyTo":"1382126170-8907-1-git-send-email-stefanbeller@googlemail.com","subject":"Re: [PATCH] git-svn documentation: Use tabs consistently within the ascii doc","fromName":"Keshav Kini","fromEmail":"keshav.kini@gmail.com","sentAt":"2013-10-19T01:37:52Z","receivedAt":"2013-10-19T01:37:52Z","isPatch":true,"sender":{"key":"keshav.kini@gmail.com","avatar":"https://avatars.githubusercontent.com/u/691290?v=4"},"body":"Stefan Beller <stefanbeller@googlemail.com> writes:\n\n> While I can understand 4 or 7 white spaces are fancy, we'd rather want\n> to use tabs throughout the whole document.\n\nYou missed lines 278 and 833.  There are also some spaces around line\n488, but maybe those are layout-relevant and so shouldn't be converted\nto tabs.\n\n-Keshav\n"},{"id":"229264","messageId":"1382384166-7331-1-git-send-email-stefanbeller@googlemail.com","threadId":"35166","inReplyTo":"87ob6mxcpb.fsf@gmail.com","subject":"[PATCH v2] git-svn docs: Use tabs consistently within the ascii doc","fromName":"Stefan Beller","fromEmail":"stefanbeller@googlemail.com","sentAt":"2013-10-21T19:36:06Z","receivedAt":"2013-10-21T19:36:06Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"While I can understand 4 or 7 white spaces are fancy, we'd rather want\nto use tabs throughout the whole document.\n\nSigned-off-by: Stefan Beller <stefanbeller@googlemail.com>\n---\n\nKeshav, thanks for the review.\nI am answering late, because my mails regarding git are sorted \nautomatically, whether these include me personally or just the mailing\nlist, and apparently you replied to just the list. \nNo need to worry, I also included lines 278 and 833 in this version.\n\nThanks,\nStefan\n\n Documentation/git-svn.txt | 26 +++++++++++++-------------\n 1 file changed, 13 insertions(+), 13 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex 2a38476..dcad890 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -175,11 +175,11 @@ Skip \"branches\" and \"tags\" of first level directories;;\n \tprecedence over '--include-paths'.\n \n --log-window-size=<n>;;\n-    Fetch <n> log entries per request when scanning Subversion history.\n-    The default is 100. For very large Subversion repositories, larger\n-    values may be needed for 'clone'/'fetch' to complete in reasonable\n-    time. But overly large values may lead to higher memory usage and\n-    request timeouts.\n+\tFetch <n> log entries per request when scanning Subversion history.\n+\tThe default is 100. For very large Subversion repositories, larger\n+\tvalues may be needed for 'clone'/'fetch' to complete in reasonable\n+\ttime. But overly large values may lead to higher memory usage and\n+\trequest timeouts.\n \n 'clone'::\n \tRuns 'init' and 'fetch'.  It will automatically create a\n@@ -275,7 +275,7 @@ first have already been pushed into SVN.\n \tFor each patch, one may answer \"yes\" (accept this patch), \"no\" (discard this\n \tpatch), \"all\" (accept all patches), or \"quit\".\n \t+\n-       'git svn dcommit' returns immediately if answer is \"no\" or \"quit\", without\n+\t'git svn dcommit' returns immediately if answer is \"no\" or \"quit\", without\n \tcommitting anything to SVN.\n \n 'branch'::\n@@ -366,12 +366,12 @@ environment). This command has the same behaviour.\n Any other arguments are passed directly to 'git log'\n \n 'blame'::\n-       Show what revision and author last modified each line of a file. The\n-       output of this mode is format-compatible with the output of\n-       `svn blame' by default. Like the SVN blame command,\n-       local uncommitted changes in the working tree are ignored;\n-       the version of the file in the HEAD revision is annotated. Unknown\n-       arguments are passed directly to 'git blame'.\n+\tShow what revision and author last modified each line of a file. The\n+\toutput of this mode is format-compatible with the output of\n+\t`svn blame' by default. Like the SVN blame command,\n+\tlocal uncommitted changes in the working tree are ignored;\n+\tthe version of the file in the HEAD revision is annotated. Unknown\n+\targuments are passed directly to 'git blame'.\n +\n --git-format;;\n \tProduce output in the same format as 'git blame', but with\n@@ -830,7 +830,7 @@ Tracking and contributing to an entire Subversion-managed project\n # View all branches and tags you have cloned:\n \tgit branch -r\n # Create a new branch in SVN\n-    git svn branch waldo\n+\tgit svn branch waldo\n # Reset your master to trunk (or any other branch, replacing 'trunk'\n # with the appropriate name):\n \tgit reset --hard svn/trunk\n-- \n1.8.4.1.511.g52c26ce\n"}]}