From 06ab60c06606613f238f3154cb27cb22d9723967 Mon Sep 17 00:00:00 2001 From: "Jason St. John" Date: Wed, 21 May 2014 14:52:26 -0400 Subject: Documentation: use "command-line" when used as a compound adjective, and fix other minor grammatical issues Signed-off-by: Jason St. John Signed-off-by: Junio C Hamano --- Documentation/user-manual.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Documentation/user-manual.txt') diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 022e74e616..d33f8849b5 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -4231,9 +4231,9 @@ Most of what `git rev-list` did is contained in `revision.c` and controls how and what revisions are walked, and more. The original job of `git rev-parse` is now taken by the function -`setup_revisions()`, which parses the revisions and the common command line +`setup_revisions()`, which parses the revisions and the common command-line options for the revision walker. This information is stored in the struct -`rev_info` for later consumption. You can do your own command line option +`rev_info` for later consumption. You can do your own command-line option parsing after calling `setup_revisions()`. After that, you have to call `prepare_revision_walk()` for initialization, and then you can get the commits one by one with the function `get_revision()`. -- cgit v1.2.3