From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Lê Duy Quang" <leduyquang753@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] Add lines to `git log --graph` to separate connected regions
Date: Mon, 08 Apr 2024 08:49:30 -0700 [thread overview]
Message-ID: <xmqqy19netx1.fsf@gitster.g> (raw)
In-Reply-To: <xmqq4jcdivgw.fsf@gitster.g> (Junio C. Hamano's message of "Sat, 06 Apr 2024 22:37:51 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> True. But because we are doing graph, shouldn't we be able to do
> better? For example, you can draw the two lineage of histories
> on different columns and ...
>
> * a2
> * a1
> * b2
> * b1
>
> ... that way, you do not need to lose one line of precious vertical
> screen real estate.
Just to save others time to go spelunking in the list archive,
"solutions" attempted and did not work in the past include
(1) wasting a line to insert a "gap" in the output.
(2) using marker different from '*' to mark each commit.
If taking the latter approach, it needs to designed to work well
with "boundary" and "left-right" options (the design to shift column
would not have to worry about these, which is another plus).
Thanks.
prev parent reply other threads:[~2024-04-08 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 5:10 [RFC PATCH 0/1] Add lines to `git log --graph` to separate connected regions Lê Duy Quang
2024-04-07 5:10 ` [RFC PATCH 1/1] Add separator lines into `git log --graph` Lê Duy Quang
2024-04-07 5:47 ` Eric Sunshine
2024-04-07 5:52 ` Eric Sunshine
2024-04-07 7:06 ` Quang Lê Duy
2024-04-07 8:35 ` Dragan Simic
2024-04-07 7:03 ` Quang Lê Duy
2024-04-07 9:07 ` Eric Sunshine
2024-04-07 5:30 ` [RFC PATCH 0/1] Add lines to `git log --graph` to separate connected regions Eric Sunshine
2024-04-07 5:37 ` Junio C Hamano
2024-04-07 6:40 ` Quang Lê Duy
2024-04-07 8:34 ` Dragan Simic
2024-04-07 8:46 ` Quang Lê Duy
2024-04-07 9:13 ` Dragan Simic
2024-04-08 15:49 ` Junio C Hamano [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy19netx1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=leduyquang753@gmail.com \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).