From: konstantin at linuxfoundation.org (Konstantin Ryabitsev)
Subject: git-fsck complains about cgit repo
Date: Wed, 15 Aug 2018 09:32:18 -0400 [thread overview]
Message-ID: <20180815133218.GA12161@chatter> (raw)
Hi, all:
Since cgit is mirrored to git.kernel.org, which gets routine fsck
treatment, I started getting the following error reports:
error: bad config line 5 in blob .gitmodules
error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob
I can easily reproduce this:
user at chatter:/tmp$ rpm -q git
git-2.17.1-3.fc28.x86_64
user at chatter:/tmp$ git clone --mirror https://git.zx2c4.com/cgit
Cloning into bare repository 'cgit.git'...
remote: Counting objects: 7043, done.
remote: Compressing objects: 100% (2679/2679), done.
remote: Total 7043 (delta 4933), reused 6211 (delta 4347)
Receiving objects: 100% (7043/7043), 8.71 MiB | 1.89 MiB/s, done.
Resolving deltas: 100% (4933/4933), done.
user at chatter:/tmp$ cd cgit.git/
user at chatter:/tmp/cgit.git$ git fsck
Checking object directories: 100% (256/256), done.
error: bad config line 5 in blob .gitmodules
error in blob 51dd1eff1edc663674df9ab85d2786a40f7ae3a5: gitmodulesParse: could not parse gitmodules blob
Checking objects: 100% (7043/7043), done.
user at chatter:/tmp/cgit.git$
Is that something that can be fixed, or should I just ignore this error?
-K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20180815/d29be375/attachment.asc>
next reply other threads:[~2018-08-15 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 13:32 konstantin [this message]
2018-08-15 14:08 ` john
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=20180815133218.GA12161@chatter \
--to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).