patchFix grammar in git-rev-parse(1).

---
 Documentation/git-rev-parse.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 59e95ad..ba65bfa 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -301,9 +301,9 @@ It is the set of commits that are reachable from
either one of
 `r1` or `r2` but not from both.

 Two other shorthands for naming a set that is formed by a commit
-and its parent commits exists.  `r1{caret}@` notation means all
+and its parent commits exist.  The `r1{caret}@` notation means all
 parents of `r1`.  `r1{caret}!` includes commit `r1` but excludes
-its all parents.
+all of its parents.

 Here are a handful of examples:

-- 
1.5.6.GIT


2008/7/6 Junio C Hamano <gitster@pobox.com>:
> "Dmitry Potapov" <dpotapov@gmail.com> writes:
>
>> On Fri, Jun 20, 2008 at 2:05 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>>>
>>> There is shortcut for rev^..rev, namely rev^! (I'm not sure if it is
>>> documented anywhere, though),
>>
>> The latter is not exactly a shortcut for the former.  You can try it at any
>> merge commit, and you will see different log. For instance, in Git repo:
>> ...
>> So, I believe, rev^! means --first-parent rev^..rev
>
> Not quite.  From Documentation/git-rev-parse.txt:
>
>    SPECIFYING RANGES
>    -----------------
>
>    Two other shorthands for naming a set that is formed by a commit
>    and its parent commits exists.  `r1{caret}@` notation means all
>    parents of `r1`.  `r1{caret}!` includes commit `r1` but excludes
>    its all parents.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Mikael Magnusson