git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCHv2 3/3] revisions.txt: language improvements

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 1, 2011, 22:05 UTC
Message-ID
<7vsju1eiff.fsf@alter.siamese.dyndns.org>
In-Reply-To
<cc9e86c7a7cacc7eea66090b38443739e6fbc672.1301649867.git.git@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
Thanks.
Show 22 quoted lines
>  Documentation/revisions.txt |   68 +++++++++++++++++++++---------------------
>  1 files changed, 34 insertions(+), 34 deletions(-)
>
> diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
> index 92bc662..25125c3 100644
> --- a/Documentation/revisions.txt
> +++ b/Documentation/revisions.txt
> @@ -2,20 +2,20 @@ SPECIFYING REVISIONS
>  --------------------
>  
>  A revision parameter '<rev>' typically, but not necessarily, names a
> -commit object.  They use what is called an 'extended SHA1'
> +commit object.  It uses what is called an 'extended SHA1'
>  syntax.  Here are various ways to spell object names.  The
> -ones listed near the end of this list are to name trees and
> +ones listed near the end of this list name trees and
>  blobs contained in a commit.
>  
>  '<sha1>', e.g. 'dae86e1950b1277e545cee180551750029cfe735', 'dae86e'::
>    The full SHA1 object name (40-byte hexadecimal string), or
> -  a substring of such that is unique within the repository.
> +  a substring that is unique within the repository.

Do we need to rephrase this a bit more, so that it would be clear that "e86e1950b" is not an abbreviated object name, even though it is a substring and may be unique within the repository?

Perhaps "a prefix of such a full SHA-1 object name that is unique..."?
Show 6 quoted lines
> @@ -79,8 +79,8 @@ the '$GIT_DIR/refs' directory or from the '$GIT_DIR/packed-refs' file.
>  
>  '@\{<n>\}', e.g. '@\{1\}'::
>    You can use the '@' construct with an empty ref part to get at a
> +  reflog of the current branch. For example, if you are on
> +  branch 'blabla' then '@\{1\}' means the same as 'blabla@\{1\}'.

Is that "a reflog of the current branch", or because there is only one reflog, should it be "the reflog of the current branch"? Ah, we mean one entry in the reflog (an entry of the reflog of the current branch), so this probably is Ok.

Show 6 quoted lines
> @@ -133,8 +133,8 @@ the '$GIT_DIR/refs' directory or from the '$GIT_DIR/packed-refs' file.
>    a commit whose commit message matches the specified regular expression.
>    This name returns the youngest matching commit which is
>    reachable from any ref.  If the commit message starts with a
> +  '!' you have to repeat that;  the special sequence ':/!',
> +  followed by something else than '!', is reserved for now.
Hmm, shouldn't it be "something OTHER than" instead?
Grammar is hard; thanks for cleaning them up.
Previous: Michael J GruberNext: Michael J Gruber
Message 19 of 20 in “revisions.txt improvements”
  1. 0/3 revisions.txt improvementsMichael J Gruber, Mar 31, 2011
  2. 1/3 revisions.txt: consistent use of quotesMichael J Gruber, Mar 31, 2011
  3. 2/3 revisions.txt: structure with a labelled listMichael J Gruber, Mar 31, 2011
  4. Jakub NarebskiMar 31, 2011
  5. Michael J GruberApr 1, 2011
  6. 3/3 revisions.txt: language improvementsMichael J Gruber, Mar 31, 2011
  7. Bert WesargMar 31, 2011
  8. Michael J GruberMar 31, 2011
  9. 0/3 revisions.txt improvementsMichael J Gruber, Apr 1, 2011
  10. 0/3 revisions.txt improvementsMichael J Gruber, Apr 4, 2011
  11. Junio C HamanoApr 4, 2011
  12. 1/3 revisions.txt: consistent use of quotesMichael J Gruber, Apr 4, 2011
  13. 2/3 revisions.txt: structure with a labelled listMichael J Gruber, Apr 4, 2011
  14. 3/3 revisions.txt: language improvementsMichael J Gruber, Apr 4, 2011
  15. 1/3 revisions.txt: consistent use of quotesMichael J Gruber, Apr 1, 2011
  16. 2/3 revisions.txt: structure with a labelled listMichael J Gruber, Apr 1, 2011
  17. Junio C HamanoApr 3, 2011
  18. 3/3 revisions.txt: language improvementsMichael J Gruber, Apr 1, 2011
  19. Junio C HamanoApr 1, 2011
  20. Michael J GruberApr 3, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.