From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: Re: rsync deprecated but promoted?
Date: Mon, 26 Sep 2005 12:23:07 -0700 [thread overview]
Message-ID: <dh9hqs$6nl$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0509261038460.3308@g5.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 26 Sep 2005, walt wrote:
>> Just because you mentioned it, I did a git-fsck-objects on my local
>> copies of your kernel tree and Junio's git tree.
>>
>> From git I got this:
>> $git-fsck-objects
>> missing commit 00d8bbd3c4bba72a6dfd48c2c0c9cbaa000f13c2
>> broken link from tag 02b2acff8bafb6d73c6513469cdda0c6c18c4138
>> to commit d5bc7eecbbb0b9f6122708bf5cd62f78ebdaafd8
>> <similar lines snipped>
>>
>> From your tree I got only this single line:
>> dangling commit 02459eaab98a6a57717bc0cacede148fc76af881
>
> That commit shouldn't be dangling, but I suspect it is harmless and is
> most likely because you have pack-files. Use "git-fsck-cache --full"
Using the --full flag made the error disappear for your kernel tree,
but had no effect on the git tree.
I neglected to mention that I use cg-clone and cg-update rather than
the git equivalents. (cogito 0.15.1 from kernel.org)
> Your git tree is quote possibly corrupted.
I recloned from http://kernel.org and I still get exactly the same fsck
errors for git, with or without the --full flag.
(I mention this only FYI. I'm not having any problems compiling or
using either git or the kernel.)
next prev parent reply other threads:[~2005-09-26 19:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 16:32 rsync deprecated but promoted? Zack Brown
2005-09-25 17:07 ` H. Peter Anvin
2005-09-25 19:06 ` Martin Coxall
2005-09-26 13:32 ` Petr Baudis
2005-09-26 14:41 ` Brian Gerst
2005-09-26 16:36 ` Petr Baudis
2005-09-26 16:47 ` Brian Gerst
2005-09-26 15:04 ` Linus Torvalds
2005-09-26 16:38 ` Petr Baudis
2005-09-26 16:43 ` Linus Torvalds
2005-11-10 23:17 ` Petr Baudis
2005-09-26 16:44 ` walt
2005-09-26 17:55 ` Linus Torvalds
2005-09-26 19:23 ` walt [this message]
2005-09-26 20:12 ` Johannes Schindelin
2005-09-26 20:19 ` Junio C Hamano
2005-09-26 22:13 ` Daniel Barkalow
2005-09-26 22:38 ` Junio C Hamano
2005-09-26 20:43 ` Petr Baudis
2005-09-27 6:35 ` hared GIT repos (was Re: rsync deprecated but promoted?) Matthias Urlichs
2005-09-27 7:13 ` shared GIT repos Junio C Hamano
2005-09-27 8:45 ` Matthias Urlichs
2005-09-27 9:59 ` Sergey Vlasov
2005-09-27 10:29 ` Matthias Urlichs
2005-09-27 15:21 ` Linus Torvalds
2005-09-27 18:36 ` hared GIT repos (was Re: rsync deprecated but promoted?) A Large Angry SCM
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='dh9hqs$6nl$1@sea.gmane.org' \
--to=wa1ter@myrealbox.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).