From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: binutils-gdb.git corruption?
Date: Mon, 22 Feb 2021 19:29:14 +0100 [thread overview]
Message-ID: <YDP3+nt7HveV1wK0@host1.jankratochvil.net> (raw)
In-Reply-To: <YDP0h+G1U7tUUSxw@elastic.org>
On Mon, 22 Feb 2021 19:14:31 +0100, Frank Ch. Eigler via Overseers wrote:
> > $ git clone git://sourceware.org/git/binutils-gdb.git;cd binutils-gdb;git annotate gdb/gdbtypes.h
> > Cloning into 'binutils-gdb'...
> > [...]
> > fatal: invalid object name: b9c1b51e45b845debb76d8658edabca70ca56079
>
> Ran a git fsck on binutils-gdb on sourceware; no problems except for some
> dangling commits.
I also ran fsck and it does not find any problem:
$ Checking object directories: 100% (256/256), done.
Checking objects: 100% (1091413/1091413), done.
Checking connectivity: 1052132, done.
dangling blob fd32115773133421ad67491a33a8701885833424
dangling commit 233d1485ae80f31da1f794ef47dd3797b2c52514
dangling blob b71c57bffbe42a67ccdf8a0b4766ccde51859a66
dangling blob 880cf124e27f5221ce99f34b7ba43c41b726b14c
dangling blob 66bdb13f31f47d074c7f32ca0e9f45b6fb80dec7
dangling blob fedbbe4f1bda044f28bdb2c7ae7b5f5b1fdc3dc6
I do not know what really happens there but it is FYI, I do not mind.
> Maybe this object only existed on your local repo?
As you can see above the reproducer makes a new repo.
Jan
next prev parent reply other threads:[~2021-02-22 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 17:56 Jan Kratochvil
2021-02-22 18:14 ` Frank Ch. Eigler
2021-02-22 18:29 ` Jan Kratochvil [this message]
2021-02-22 19:08 ` Frank Ch. Eigler
2021-02-22 19:24 ` Jan Kratochvil
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=YDP3+nt7HveV1wK0@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=overseers@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).