diff options
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-bisect.txt | 2 | ||||
| -rw-r--r-- | Documentation/git-gui.txt | 4 | ||||
| -rw-r--r-- | Documentation/gitcore-tutorial.txt | 2 | ||||
| -rw-r--r-- | Documentation/gittutorial.txt | 2 |
4 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt index c794914366..c7981efcd9 100644 --- a/Documentation/git-bisect.txt +++ b/Documentation/git-bisect.txt @@ -98,7 +98,7 @@ During the bisection process, you can say $ git bisect visualize ------------ -to see the currently remaining suspects in `gitk`. `visualize` is a bit +to see the currently remaining suspects in 'gitk'. `visualize` is a bit too long to type and `view` is provided as a synonym. If 'DISPLAY' environment variable is not set, 'git-log' is used diff --git a/Documentation/git-gui.txt b/Documentation/git-gui.txt index f067772baa..a73201d933 100644 --- a/Documentation/git-gui.txt +++ b/Documentation/git-gui.txt @@ -16,9 +16,9 @@ on allowing users to make changes to their repository by making new commits, amending existing ones, creating branches, performing local merges, and fetching/pushing to remote repositories. -Unlike `gitk`, 'git-gui' focuses on commit generation +Unlike 'gitk', 'git-gui' focuses on commit generation and single file annotation and does not show project history. -It does however supply menu actions to start a `gitk` session from +It does however supply menu actions to start a 'gitk' session from within 'git-gui'. 'git-gui' is known to work on all popular UNIX systems, Mac OS X, diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt index 2bbe7dea37..3eba973a2b 100644 --- a/Documentation/gitcore-tutorial.txt +++ b/Documentation/gitcore-tutorial.txt @@ -878,7 +878,7 @@ means: normally it will just show you your current `HEAD`) and their histories. You can also see exactly how they came to be from a common source. -Anyway, let's exit `gitk` (`^Q` or the File menu), and decide that we want +Anyway, let's exit 'gitk' (`^Q` or the File menu), and decide that we want to merge the work we did on the `mybranch` branch into the `master` branch (which is currently our `HEAD` too). To do that, there's a nice script called 'git-merge', which wants to know which branches you want diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt index 2c4346c9e8..e71b561172 100644 --- a/Documentation/gittutorial.txt +++ b/Documentation/gittutorial.txt @@ -529,7 +529,7 @@ then merged back together, the order in which 'git-log' presents those commits is meaningless. Most projects with multiple contributors (such as the linux kernel, -or git itself) have frequent merges, and `gitk` does a better job of +or git itself) have frequent merges, and 'gitk' does a better job of visualizing their history. For example, ------------------------------------- |