Documentation/rev-list-options.txt: fix some grammatical issues and typos
Various fixes: - fix typos (e.g. "show" -> "shown") - use "regular expression(s)" instead of "regexp" where appropriate - reword some sentences for easier reading - fix/improve some grammatical issues (e.g. comma usage) - add missing articles (e.g. "the") - change "E-mail" to "email" Signed-off-by: Jason St. John <jstjohn@purdue.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jason St. John committed
Nov 14, 2013 at 20:34 UTC
19d6eb412cd6f47960737dd66bf1d1866e26986f
1 file changed
+14
-13
Documentation/rev-list-options.txt
+14
-13
@@ -68,7 +68,8 @@ if it is part of the log message.
68
69
-i::
70
--regexp-ignore-case::
71
- Match the regexp limiting patterns without regard to letters case.
71
+ Match the regular expression limiting patterns without regard to letter
72
+ case.
73
74
--basic-regexp::
75
Consider the limiting patterns to be basic regular expressions;
@@ -85,7 +86,7 @@ if it is part of the log message.
86
pattern as a regular expression).
87
88
--perl-regexp::
88
- Consider the limiting patterns to be Perl-compatible regexp.
89
+ Consider the limiting patterns to be Perl-compatible regular expressions.
90
Requires libpcre to be compiled in.
91
92
--remove-empty::
@@ -191,9 +192,9 @@ endif::git-rev-list[]
192
For example, if you have two branches, `A` and `B`, a usual way
193
to list all commits on only one side of them is with
194
`--left-right` (see the example below in the description of
194
-the `--left-right` option). It however shows the commits that were cherry-picked
195
-from the other branch (for example, ``3rd on b'' may be cherry-picked
196
-from branch A). With this option, such pairs of commits are
195
+the `--left-right` option). However, it shows the commits that were
196
+cherry-picked from the other branch (for example, ``3rd on b'' may be
197
+cherry-picked from branch A). With this option, such pairs of commits are
198
excluded from the output.
199
200
--left-only::
@@ -447,7 +448,7 @@ The effect of this is best shown by way of comparing to
448
`---------'
449
-----------------------------------------------------------------------
450
+
450
-Note the major differences in `N`, `P` and `Q` over `--full-history`:
451
+Note the major differences in `N`, `P`, and `Q` over `--full-history`:
452
+
453
--
454
* `N`'s parent list had `I` removed, because it is an ancestor of the
@@ -467,7 +468,7 @@ Finally, there is a fifth simplification mode available:
468
Limit the displayed commits to those directly on the ancestry
469
chain between the ``from'' and ``to'' commits in the given commit
470
range. I.e. only display commits that are ancestor of the ``to''
470
- commit, and descendants of the ``from'' commit.
471
+ commit and descendants of the ``from'' commit.
472
+
473
As an example use case, consider the following commit history:
474
+
@@ -631,9 +632,9 @@ These options are mostly targeted for packing of Git repositories.
632
--no-walk[=(sorted|unsorted)]::
633
Only show the given commits, but do not traverse their ancestors.
634
This has no effect if a range is specified. If the argument
634
- `unsorted` is given, the commits are show in the order they were
635
+ `unsorted` is given, the commits are shown in the order they were
636
given on the command line. Otherwise (if `sorted` or no argument
636
- was given), the commits are show in reverse chronological order
637
+ was given), the commits are shown in reverse chronological order
638
by commit time.
639
640
--do-walk::
@@ -656,7 +657,7 @@ include::pretty-options.txt[]
657
--date=(relative|local|default|iso|rfc|short|raw)::
658
Only takes effect for dates shown in human-readable format, such
659
as when using `--pretty`. `log.date` config variable sets a default
659
- value for log command's `--date` option.
660
+ value for the log command's `--date` option.
661
+
662
`--date=relative` shows dates relative to the current time,
663
e.g. ``2 hours ago''.
@@ -666,9 +667,9 @@ e.g. ``2 hours ago''.
667
`--date=iso` (or `--date=iso8601`) shows timestamps in ISO 8601 format.
668
+
669
`--date=rfc` (or `--date=rfc2822`) shows timestamps in RFC 2822
669
-format, often found in E-mail messages.
670
+format, often found in email messages.
671
+
671
-`--date=short` shows only date but not time, in `YYYY-MM-DD` format.
672
+`--date=short` shows only the date, but not the time, in `YYYY-MM-DD` format.
673
+
674
`--date=raw` shows the date in the internal raw Git format `%s %z` format.
675
+
@@ -749,7 +750,7 @@ ifndef::git-rev-list[]
750
Diff Formatting
751
~~~~~~~~~~~~~~~
752
752
-Below are listed options that control the formatting of diff output.
753
+Listed below are options that control the formatting of diff output.
754
Some of them are specific to linkgit:git-rev-list[1], however other diff
755
options may be given. See linkgit:git-diff-files[1] for more options.
756