From: Junio C Hamano <gitster@pobox.com>
To: Alexandre Badez <alexandre@badez.eu>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>
Subject: Re: Git log --decorate show prefetch objects
Date: Thu, 04 Apr 2024 09:56:30 -0700 [thread overview]
Message-ID: <xmqqh6gh12yp.fsf@gitster.g> (raw)
In-Reply-To: <5a16d4e3-6fa4-45f3-ae79-576f3fa80d44@badez.eu> (Alexandre Badez's message of "Thu, 4 Apr 2024 12:16:20 +0200")
Alexandre Badez <alexandre@badez.eu> writes:
> # What did you do before the bug happened? (Steps to reproduce your issue)
>
> <on a git repository not fetch from a "long" time so you have missing
> branches and/or objects>
>
> git maintenance run --task=prefetch
>
> git log --oneline --decorate --all --graph
I do not use the prefetch stuff, but unfortunately the person who
was most familiar with "maintenance" are no longer active on this
list, so let me take a crack.
I think your complaint is that "--all" really means "all", not just
"heads" and "tags" but also includes "prefetch", while the prefetch
hierarchy is not included in the "--decorate" sources.
What does
$ git log --oneline --branches --tags --decorate --graph
show, and is it closer to what you expected (note: this is not a
direct suggestion of a workaround---trying to gauge what the
direction is to move forward)?
Thanks.
next prev parent reply other threads:[~2024-04-04 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 10:16 Git log --decorate show prefetch objects Alexandre Badez
2024-04-04 16:56 ` Junio C Hamano [this message]
2024-04-04 21:37 ` Alexandre Badez
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=xmqqh6gh12yp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alexandre@badez.eu \
--cc=git@vger.kernel.org \
--cc=stolee@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 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.