Skip to content

Commit 55ae30c

Browse files
authored
tools: grammar changes in oldv usage (#22515)
1 parent b114254 commit 55ae30c

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

cmd/tools/oldv.v

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,24 +4,24 @@ import scripting
44
import vgit
55

66
const tool_version = '0.0.4'
7-
const tool_description = ' Checkout an old V and compile it as it was on specific commit.
8-
| This tool is useful, when you want to discover when something broke.
9-
| It is also useful, when you just want to experiment with an older historic V.
7+
const tool_description = ' Checkout an old version of V and compile it as it was on a specific commit.
8+
| This tool is useful when you want to discover when something broke.
9+
| It is also useful when you just want to experiment with an older, historic V.
1010
|
11-
| The VCOMMIT argument can be a git commitish like HEAD or master and so on.
12-
| When oldv is used with git bisect, you probably want to give HEAD. For example:
11+
| The VCOMMIT argument can be a git commit object like HEAD or master and so on.
12+
| When oldv is used with git bisect, you probably want to use HEAD. For example:
1313
| git bisect start
1414
| git bisect bad
1515
| git checkout known_good_commit
1616
| git bisect good
17-
| ## Now git will automatically checkout a middle commit between the bad and the good
18-
| cmd/tools/oldv --bisect --command="run commands in oldv folder, to verify if the commit is good or bad"
19-
| ## See what the result is, and either do: ...
17+
| ## git will automatically checkout a middle commit between the bad and the good
18+
| cmd/tools/oldv --bisect --command="run commands in oldv folder, to verify if the commit is good or bad
19+
| ## Examine the results, and either do: ...
2020
| git bisect good
2121
| ## ... or do:
2222
| git bisect bad
23-
| ## Now you just repeat the above steps, each time running oldv with the same command, then mark the result as good or bad,
24-
| ## until you find the commit, where the problem first occurred.
23+
| ## Repeat the above steps, each time running oldv with the same command, then mark the result as good
24+
| ## or bad until you find the commit where the problem first occurred.
2525
| ## When you finish, do not forget to do:
2626
| git bisect reset'.strip_margin()
2727

0 commit comments

Comments
 (0)