{"thread":{"id":"7966","subject":"[git-svn PATCH] Fix markup in git-svn man page","startedAt":"2007-05-04T07:03:22Z","lastAt":"2007-05-05T13:02:17Z","messageCount":4,"participants":["Karl Hasselström","Eric Wong","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"41010","messageId":"20070504070003.9117.75385.stgit@yoghurt","threadId":"7966","inReplyTo":null,"subject":"[git-svn PATCH] Fix markup in git-svn man page","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-05-04T07:03:22Z","receivedAt":"2007-05-04T07:03:22Z","isPatch":true,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"Some of the existing markup was just plain broken, and some subcommand\noptions weren't indented properly.\n\nSigned-off-by: Karl Hasselström \n---\n\nI poked at the markup with a stick until it rendered well (as both man\nand html), but I really don't know much about asciidoc markup, so some\nsanity-checking by a third party is probably a good idea.\n\n Documentation/git-svn.txt | 32 +++++++++++++-------------------\n 1 files changed, 13 insertions(+), 19 deletions(-)\n\ndiff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt\nindex fcdeeaa..c0d7d95 100644\n--- a/Documentation/git-svn.txt\n+++ b/Documentation/git-svn.txt\n@@ -38,32 +38,30 @@ COMMANDS\n \targument. Normally this command initializes the current\n \tdirectory.\n \n--T::\n---trunk=::\n--t::\n---tags=::\n--b::\n---branches=::\n+-T;;\n+--trunk=;;\n+-t;;\n+--tags=;;\n+-b;;\n+--branches=;;\n \tThese are optional command-line options for init. Each of\n \tthese flags can point to a relative repository path\n \t(--tags=project/tags') or a full url\n \t(--tags=https://foo.org/project/tags)\n-\n---no-metadata::\n+--no-metadata;;\n \tSet the 'noMetadata' option in the [svn-remote] config.\n---use-svm-props::\n+--use-svm-props;;\n \tSet the 'useSvmProps' option in the [svn-remote] config.\n---use-svnsync-props::\n+--use-svnsync-props;;\n \tSet the 'useSvnsyncProps' option in the [svn-remote] config.\n---rewrite-root=::\n+--rewrite-root=;;\n \tSet the 'rewriteRoot' option in the [svn-remote] config.\n---username=::\n+--username=;;\n \tFor transports that SVN handles authentication for (http,\n \thttps, and plain svn), specify the username. For other\n \ttransports (eg svn+ssh://), you must include the username in\n \tthe URL, eg svn+ssh://foo@svn.bar.com/project\n-\n---prefix=::\n+--prefix=;;\n \tThis allows one to specify a prefix which is prepended\n \tto the names of remotes if trunk/branches/tags are\n \tspecified. The prefix does not automatically include a\n@@ -73,7 +71,6 @@ COMMANDS\n \trepository.\n \n 'fetch'::\n-\n \tFetch unfetched revisions from the Subversion remote we are\n \ttracking. The name of the [svn-remote \"...\"] section in the\n \t.git/config file may be specified as an optional command-line\n@@ -104,14 +101,11 @@ accepts. However '--fetch-all' only fetches from the current\n \n Like 'git-rebase'; this requires that the working tree be clean\n and have no uncommitted changes.\n-+\n---\n+\n -l;;\n --local;;\n \tDo not fetch remotely; only run 'git-rebase' against the\n \tlast fetched commit from the upstream SVN.\n---\n-+\n \n 'dcommit'::\n \tCommit each diff from a specified head directly to the SVN\n"},{"id":"41016","messageId":"20070504080620.GC17526@muzzle","threadId":"7966","inReplyTo":"20070504070003.9117.75385.stgit@yoghurt","subject":"Re: [git-svn PATCH] Fix markup in git-svn man page","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2007-05-04T08:06:20Z","receivedAt":"2007-05-04T08:06:20Z","isPatch":true,"sender":{"key":"e@80x24.org","avatar":null},"body":"Karl Hasselström wrote:\n> Some of the existing markup was just plain broken, and some subcommand\n> options weren't indented properly.\n> \n> Signed-off-by: Karl Hasselström \n> ---\n> \n> I poked at the markup with a stick until it rendered well (as both man\n> and html), but I really don't know much about asciidoc markup, so some\n> sanity-checking by a third party is probably a good idea.\n\nI don't know much about it, either. They take way too long for me to\nbuild, so I've mostly just guessed the syntax based on the existing\ndocumentation and let other people fix it for me :)\n\n-- \nEric Wong\n"},{"id":"41097","messageId":"7vslacs0p6.fsf@assigned-by-dhcp.cox.net","threadId":"7966","inReplyTo":"20070504070003.9117.75385.stgit@yoghurt","subject":"Re: [git-svn PATCH] Fix markup in git-svn man page","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-05-04T22:06:45Z","receivedAt":"2007-05-04T22:06:45Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Looks sane to me. I did not know about double-semicolon, which\nis mentioned in the user guide documentation at the asciidoc\nsite but I could not tell how it is different from double-colon\nform. I am guessing (from the behaviour after applying your\npatch) that it allows second level of listing...\n"},{"id":"41143","messageId":"20070505130217.GA3379@diana.vm.bytemark.co.uk","threadId":"7966","inReplyTo":"7vslacs0p6.fsf@assigned-by-dhcp.cox.net","subject":"Re: [git-svn PATCH] Fix markup in git-svn man page","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-05-05T13:02:17Z","receivedAt":"2007-05-05T13:02:17Z","isPatch":true,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2007-05-04 15:06:45 -0700, Junio C Hamano wrote:\n\n> Looks sane to me. I did not know about double-semicolon, which is\n> mentioned in the user guide documentation at the asciidoc site but I\n> could not tell how it is different from double-colon form. I am\n> guessing (from the behaviour after applying your patch) that it\n> allows second level of listing...\n\nYes, it was used that way in the parts of the man page that already\nlooked OK, so I just copied it. If it looks good to you too, it must\nbe correct. :-)\n\n-- \nKarl Hasselström, kha@treskal.com\n www.treskal.com/kalle\n"}]}