{"thread":{"id":"47174","subject":"[PATCH v4] bisect: mention \"view\" as an alternative to \"visualize\"","startedAt":"2017-11-12T09:31:12Z","lastAt":"2017-11-12T09:31:12Z","messageCount":1,"participants":["Robert P. J. Day"],"isPatch":true,"patchVersion":4,"patchTotal":null},"messages":[{"id":"332313","messageId":"alpine.LFD.2.21.1711120426540.29973@localhost.localdomain","threadId":"47174","inReplyTo":null,"subject":"[PATCH v4] bisect: mention \"view\" as an alternative to \"visualize\"","fromName":"Robert P. J. Day","fromEmail":"rpjday@crashcourse.ca","sentAt":"2017-11-12T09:30:38Z","receivedAt":"2017-11-12T09:31:12Z","isPatch":true,"sender":{"key":"rpjday@crashcourse.ca","avatar":"https://avatars.githubusercontent.com/u/226084077?v=4"},"body":"Tweak a small number of files to mention \"view\" as an alternative to\n\"visualize\".\n\nSigned-off-by: Robert P. J. Day <rpjday@crashcourse.ca>\n\n---\n\n  ok, let's see if this one is getting close ...\n\n Documentation/git-bisect.txt | 13 ++++++-------\n builtin/bisect--helper.c     |  2 +-\n git-bisect.sh                |  4 ++--\n 3 files changed, 9 insertions(+), 10 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex 6c42abf07..4a1417bdc 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -23,7 +23,7 @@ on the subcommand:\n  git bisect terms [--term-good | --term-bad]\n  git bisect skip [(<rev>|<range>)...]\n  git bisect reset [<commit>]\n- git bisect visualize\n+ git bisect (visualize|view)\n  git bisect replay <logfile>\n  git bisect log\n  git bisect run <cmd>...\n@@ -193,24 +193,23 @@ git bisect start --term-new fixed --term-old broken\n Then, use `git bisect <term-old>` and `git bisect <term-new>` instead\n of `git bisect good` and `git bisect bad` to mark commits.\n\n-Bisect visualize\n-~~~~~~~~~~~~~~~~\n+Bisect visualize/view\n+~~~~~~~~~~~~~~~~~~~~~\n\n To see the currently remaining suspects in 'gitk', issue the following\n-command during the bisection process:\n+command during the bisection process (the subcommand `view` can be used\n+as an alternative to `visualize`):\n\n ------------\n $ git bisect visualize\n ------------\n\n-`view` may also be used as a synonym for `visualize`.\n-\n If the `DISPLAY` environment variable is not set, 'git log' is used\n instead.  You can also give command-line options such as `-p` and\n `--stat`.\n\n ------------\n-$ git bisect view --stat\n+$ git bisect visualize --stat\n ------------\n\n Bisect log and bisect replay\ndiff --git a/builtin/bisect--helper.c b/builtin/bisect--helper.c\nindex 35d2105f9..4b5fadcbe 100644\n--- a/builtin/bisect--helper.c\n+++ b/builtin/bisect--helper.c\n@@ -46,7 +46,7 @@ static int check_term_format(const char *term, const char *orig_term)\n \t\treturn error(_(\"'%s' is not a valid term\"), term);\n\n \tif (one_of(term, \"help\", \"start\", \"skip\", \"next\", \"reset\",\n-\t\t\t\"visualize\", \"replay\", \"log\", \"run\", \"terms\", NULL))\n+\t\t\t\"visualize\", \"view\", \"replay\", \"log\", \"run\", \"terms\", NULL))\n \t\treturn error(_(\"can't use the builtin command '%s' as a term\"), term);\n\n \t/*\ndiff --git a/git-bisect.sh b/git-bisect.sh\nindex 0138a8860..a82256e34 100755\n--- a/git-bisect.sh\n+++ b/git-bisect.sh\n@@ -1,6 +1,6 @@\n #!/bin/sh\n\n-USAGE='[help|start|bad|good|new|old|terms|skip|next|reset|visualize|replay|log|run]'\n+USAGE='[help|start|bad|good|new|old|terms|skip|next|reset|visualize|view|replay|log|run]'\n LONG_USAGE='git bisect help\n \tprint this long help message.\n git bisect start [--term-{old,good}=<term> --term-{new,bad}=<term>]\n@@ -20,7 +20,7 @@ git bisect next\n \tfind next bisection to test and check it out.\n git bisect reset [<commit>]\n \tfinish bisection search and go back to commit.\n-git bisect visualize\n+git bisect (visualize|view)\n \tshow bisect status in gitk.\n git bisect replay <logfile>\n \treplay bisection log.\n\n\n-- \n\n========================================================================\nRobert P. J. Day                                 Ottawa, Ontario, CANADA\n                        http://crashcourse.ca\n\nTwitter:                                       http://twitter.com/rpjday\nLinkedIn:                               http://ca.linkedin.com/in/rpjday\n========================================================================\n"}]}