From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: git-svn goes into infinite loop rebuilding rev_map
Date: Fri, 16 May 2008 13:15:56 -0400 [thread overview]
Message-ID: <4aca3dc20805161015l28d1e4a2u318c1bc23bb5b925@mail.gmail.com> (raw)
Starting last night, for no particularly obvious reason, git-svn fetch
(or git-svn rebase or any command that does naything interesting) on
gcc.gnu.org's repo causes git-svn to do the following:
-bash-3.00$ git-svn fetch
Rebuilding .git/svn/trunk/.rev_map.138bc75d-0d04-0410-961f-82ee72b054a4 ...
Done rebuilding .git/svn/trunk/.rev_map.138bc75d-0d04-0410-961f-82ee72b054a4
Rebuilding .git/svn/trunk/.rev_map.138bc75d-0d04-0410-961f-82ee72b054a4 ...
<repeat forever>
I checked the obvious things. There is no permissions problem, strace
doesn't show the writes failing, etc.
git-fsck shows nothing as being obviously wrong.
This just suddenly started happening with no obvious reason (we fire
off git-svn fetch and rebase on the repo when cvs commits happen).
git-log shows the last processed rev was:
commit e66b310fb9a3ddc7ed5143db3c468711c8a36d08
Author: uros <uros@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Thu May 15 14:38:23 2008 +0000
* config/i386/sse.md (*vec_concatv2sf_sse4_1): Add "m" constraint
to alternative 4 of operand 2.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@135364
138bc75d-0d04-0410-961f-82ee72b054a4
I'm happy to provide anything i can to get the problem fixed, but not
being a git expert, i have no idea what is up here.
next reply other threads:[~2008-05-16 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 17:15 Daniel Berlin [this message]
2008-05-16 17:48 ` git-svn goes into infinite loop rebuilding rev_map Kevin Ballard
2008-05-16 18:02 ` Daniel Berlin
2008-05-19 3:30 ` Daniel Berlin
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=4aca3dc20805161015l28d1e4a2u318c1bc23bb5b925@mail.gmail.com \
--to=dberlin@dberlin.org \
--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).