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

Re: [PATCH] Improve revisions.txt

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 5, 2012, 18:06 UTC
Message-ID
<7vpq8aqdzb.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1341506716-97920-1-git-send-email-max@quendi.de>
Max Horn <max@quendi.de> writes:
> One section talked about <name> when only <refname> was defined.
Thanks.  This is a definite improvement.
> And the description for r1^! was incorrect, talking about "parents"
> (which I understand as meaning direct parent commits),
> when really all ancestors were meant.

What makes ^! exclude "all ancestors" is that you fed it to rev-list or log. r1^! really means "mark r1 as interesting, but mark its direct parents as uninteresting". r1^@ means "r1's direct parents are interesting". For example, "git show -s r1^@" will show the direct parents of r1 but not its ancestors.

While there is nothing wrong in the updated descriptin per-se (because it is about "specifying ranges", aka "feeding these to rev-list or log, here is what happens"), I am torn about this part of the patch. Perhaps ^! and ^@ may also deserve to be described as a way to give individual revisions (not "specifying ranges")?

I dunno.
Show 14 quoted lines
> Finally I added a few more examples (in particular one for "B..C")
> that helped me understand the whole thing.
> ...
> @@ -224,7 +225,10 @@ Here are a handful of examples:
>     D F              G H I J D F
>     ^G D             H D
>     ^D B             E I J F B
> +   B..C             C
>     B...C            G H D E B C
>     ^D B C           E I J F B C
> +   C                I J F C
>     C^@              I J F
> +   B^! C            B C
>     F^! D            G H D F
Previous: Max HornNext: Max Horn
Message 2 of 9 in “Improve revisions.txt”
  1. Improve revisions.txtMax Horn, Jul 5, 2012
  2. Junio C HamanoJul 5, 2012
  3. 1/2 Make <refname> documentation more consistent.Max Horn, Jul 6, 2012
  4. 2/2 Document rev^! and rev^@ as revision specifiersMax Horn, Jul 6, 2012
  5. Junio C HamanoJul 6, 2012
  6. Max HornJul 6, 2012
  7. Junio C HamanoJul 6, 2012
  8. Max HornJul 9, 2012
  9. Junio C HamanoJul 23, 2012

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.