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

Re: [PATCH] Inconsistency between git log and git rev-parse for ^HEAD^@

From
AGAndreas Gruenbacher <agruenba@redhat.com>
Date
Mar 18, 2017, 21:26 UTC
Message-ID
<CAHc6FU7xdyU-c5x3jGqy20g9N=BQo9KcWsZjh39eFX1mk+kSvQ@mail.gmail.com>
In-Reply-To
<xmqq7f3m1gqd.fsf@gitster.mtv.corp.google.com>
On Sat, Mar 18, 2017 at 9:18 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> Andreas Gruenbacher <agruenba@redhat.com> writes:
>
>> Hello,
>>
>> the log and rev-parse commands both support the rev^@ syntax which stands for
>> all parents of rev.  The log command also supports ^rev^@ to exclude all of the
>> parents of rev, but rev-parse does not.  Should this be fixed?
>>
>> If so, the following patch would be a start.
>
> Hmph, would ^A..B and ^A...B also be turned into B..A and B...A in a
> similar way?  I think the latter would not make much sense but ^A..B
> might.

The previous patch supports neither. I agree about ^A...B, and I don't think supporting ^A..B is relevant.

> In any case, accepting ^rev^@ may make sense nevertheless.
Andreas
Previous: Junio C Hamano
Message 3 of 3 in “Inconsistency between git log and git rev-parse for ^HEAD^@”
  1. Inconsistency between git log and git rev-parse for ^HEAD^@Andreas Gruenbacher, Mar 18, 2017
  2. Junio C HamanoMar 18, 2017
  3. Andreas GruenbacherMar 18, 2017

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.