From: Fernando Ramos <greenfoo@u92.eu>
To: Pablo <pabloosabaterr@gmail.com>
Cc: git@vger.kernel.org, me@ttaylorr.com
Subject: Re: [RFC] Show empty root commits when using --simplify-by-decoration
Date: Sat, 4 Apr 2026 22:05:03 +0200 [thread overview]
Message-ID: <adFu7wLmro5A9NDr@x395.localdomain> (raw)
In-Reply-To: <CAN5EUNTUDT7FMNYTOnTA_GJJXa2eZZL=RhJHfA6PfJvFSSHL-g@mail.gmail.com>
On 26/04/04 06:08PM, Pablo wrote:
> >
> > Issue (2) can be "fixed" by using a diferent character (for example "I") for
> > root commits...
>
> This has actually been discussed before and it was ruled out some years ago.
> https://lore.kernel.org/git/xmqqwnwajbuj.fsf@gitster.c.googlers.com/
>
> You might find interesting a patch I'm working on that tackles that
> confusing look when two "parentless" commits are stacked.
> https://lore.kernel.org/git/20260404092425.550346-1-pabloosabaterr@gmail.com/
>
> This answer from junio might be helpful as well:
> https://lore.kernel.org/git/xmqqbjfzn6ku.fsf@gitster.g/
Ups... I completely missed those on the very quick search I did on the topic.
Sorry. I will ignore "Issue (2)" then and wait for your patch :)
> One more thing, even if it's an RFC it would be much easier for reviewers if
> the patches were sent as git format-patch (one each email) with a cover
> letter, discussing your RFC, so anyone can use git am and b4 to apply the
> patches.
Thanks, I was not sure whether I should send individual emails for this,
considering that, after the feedback, they might be dropped. But now I know.
Once I receive freedback on whether the "fix" for "Issue (1)" is a good idea or
not, I will resubmit a proper patch.
Thanks.
prev parent reply other threads:[~2026-04-04 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 15:17 [RFC] Show empty root commits when using --simplify-by-decoration Fernando Ramos
2026-04-04 16:08 ` Pablo
2026-04-04 20:05 ` Fernando Ramos [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=adFu7wLmro5A9NDr@x395.localdomain \
--to=greenfoo@u92.eu \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=pabloosabaterr@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox