diff options
| author | Junio C Hamano <gitster@pobox.com> | 2016-05-18 14:40:13 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-05-18 14:40:14 -0700 |
| commit | 8d61f0f07d078f4ea05d0b70511b0c8c39d8e863 (patch) | |
| tree | 2b4a63ffba084de5181b3f0e1cf4e4b80dfc7713 | |
| parent | 977cb3e2c5692234159b7f879eaccef946a0f9cb (diff) | |
| parent | 2e39a246071eb7bc9153e48e0c9416f069ac2a17 (diff) | |
| download | git-8d61f0f07d078f4ea05d0b70511b0c8c39d8e863.tar.gz | |
Merge branch 'rn/glossary-typofix' into HEAD
* rn/glossary-typofix:
Documentation: fix typo 'In such these cases'
| -rw-r--r-- | Documentation/glossary-content.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt index cafc284359..8ad29e61a9 100644 --- a/Documentation/glossary-content.txt +++ b/Documentation/glossary-content.txt @@ -145,7 +145,7 @@ current branch integrates with) obviously do not work, as there is no A fast-forward is a special type of <<def_merge,merge>> where you have a <<def_revision,revision>> and you are "merging" another <<def_branch,branch>>'s changes that happen to be a descendant of what - you have. In such these cases, you do not make a new <<def_merge,merge>> + you have. In such a case, you do not make a new <<def_merge,merge>> <<def_commit,commit>> but instead just update to his revision. This will happen frequently on a <<def_remote_tracking_branch,remote-tracking branch>> of a remote |