From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: [RFH] WTF did we change in git-fsck recently?
Date: Fri, 20 Apr 2007 17:30:31 -0700 [thread overview]
Message-ID: <7vps5ywouw.fsf@assigned-by-dhcp.cox.net> (raw)
I noticed that "git-fsck --full" from 'master' takes forever to
fsck the kernel repository (I left it running for 2 hours before
killing it), while the one from 'maint' (or 1.5.1.1 which is
installed on kernel.org) finishes within 2 or 3 minutes. There
is some serious breakages there.
Rings a bell?
next reply other threads:[~2007-04-21 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 0:30 Junio C Hamano [this message]
2007-04-21 1:24 ` [RFH] WTF did we change in git-fsck recently? Linus Torvalds
2007-04-21 1:30 ` Linus Torvalds
2007-04-21 2:17 ` Junio C Hamano
2007-04-21 20:36 ` Automated bisect success story Junio C Hamano
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=7vps5ywouw.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.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