From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Date: Thu, 29 Feb 2024 10:03:50 GMT
Subject: Re: [RFD] should "git log --graph -g" work and if so how?
Message-ID: <ZeBWhkSwec7PmQID@ugly>
In-Reply-To: <xmqqo7c5n0ob.fsf@gitster.g>

On Sat, Feb 24, 2024 at 11:04:52AM -0800, Junio C Hamano wrote:
>Now, if I could run
>
>    $ git log --oneline --graph -g --since=2024-02-20 --boundary
>
>on the result, such a history might look like this:
>
>    * snapshot as of 2024-02-24 (HEAD)
>    | * snapshot as of 2024-02-23 (HEAD@{1})
>    |/
>    | * snapshot as of 2024-02-22 (HEAD@{2})
>    |/
>    * add 'bar' (HEAD~1)
>    o add 'foo' (HEAD~2)
>
>to show the same history.
>
>Unfortunately, "--graph" and "-g" does not mix X-<.
>
>So, the RFD is,
>
> (1) Should "git log" learn a trick to show a history like this in a
>     readable way?  Does it have utility outside this use case of
>     mine?  I am not interested in adding a new feature just for
>     myself ;-)
>
i'm not sure i fully understand your use case; i failed to extract the
conceptual requirements from your description.

but as a "heavy revisionist", i would appreciate it very much if there
was a convenient way to list and diff revisions of the same logical
commit (ideally omitting empty rebases). sort of like a range-diff on
steroids.

this would certainly require correlating the reflog with some stable
commit ids, like gerrit and jj maintain.