From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: binutils-gdb.git corruption?
Date: Mon, 22 Feb 2021 13:14:31 -0500 [thread overview]
Message-ID: <YDP0h+G1U7tUUSxw@elastic.org> (raw)
In-Reply-To: <YDPwO6loHBDh68tm@host1.jankratochvil.net>
Hi -
> $ 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. Maybe this object only existed on your local repo?
- FChE
next prev parent reply other threads:[~2021-02-22 18:14 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 [this message]
2021-02-22 18:29 ` Jan Kratochvil
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=YDP0h+G1U7tUUSxw@elastic.org \
--to=fche@elastic.org \
--cc=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).