From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFD] should "git log --graph -g" work and if so how?
Date: Thu, 29 Feb 2024 11:03:50 +0100 [thread overview]
Message-ID: <ZeBWhkSwec7PmQID@ugly> (raw)
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.
prev parent reply other threads:[~2024-02-29 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 19:04 [RFD] should "git log --graph -g" work and if so how? Junio C Hamano
2024-02-29 10:03 ` Oswald Buddenhagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZeBWhkSwec7PmQID@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.