From: Peter Eisentraut <peter_e@gmx.net>
To: git@vger.kernel.org
Subject: cvsimport infinite loop
Date: Sat, 9 Feb 2008 12:45:36 +0100 [thread overview]
Message-ID: <200802091245.38578.peter_e@gmx.net> (raw)
I'm trying to convert the PostgreSQL CVS to Git, using Git 1.5.4 (but
the problem also occurs with earlier versions). To reproduce:
$ rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs cvsroot/
$ git-cvsimport -v -d $PWD/cvsroot pgsql
This runs for a while and then messages like this are repeating:
WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
src/include/c.h:1.17=after, src/include/executor/nodeNestloop.h:1.2=before. Treated as 'before'
WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
src/include/c.h:1.17=after, src/include/executor/nodeResult.h:1.2=before. Treated as 'before'
WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
src/include/c.h:1.17=after, src/include/executor/nodeSeqscan.h:1.3=before. Treated as 'before'
...
WARNING: Invalid PatchSet 2064, Tag REL7_1_BETA2:
src/include/c.h:1.18=after, src/include/executor/nodeNestloop.h:1.3=before. Treated as 'before'
WARNING: Invalid PatchSet 2064, Tag REL7_1_BETA2:
src/include/c.h:1.18=after, src/include/executor/nodeResult.h:1.3=before. Treated as 'before'
WARNING: Invalid PatchSet 2064, Tag REL7_1_BETA2:
src/include/c.h:1.18=after, src/include/executor/nodeSeqscan.h:1.4=before. Treated as 'before'
...
...
...
and then they start again
WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
src/include/c.h:1.17=after, src/include/executor/nodeNestloop.h:1.2=before. Treated as 'before'
WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
src/include/c.h:1.17=after, src/include/executor/nodeResult.h:1.2=before. Treated as 'before'
WARNING: Invalid PatchSet 2062, Tag REL7_1_BETA2:
src/include/c.h:1.17=after, src/include/executor/nodeSeqscan.h:1.3=before. Treated as 'before'
I've let this run all night and it doesn't stop.
I don't want to exclude the possibility that the CVS repository has had some
funny business done to it over the years, but surely an infinite loop
shouldn't happen in any case. Please advise.
next reply other threads:[~2008-02-09 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 11:45 Peter Eisentraut [this message]
2008-02-09 12:01 ` cvsimport infinite loop Martin Langhoff
2008-02-10 16:38 ` Michael Haggerty
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=200802091245.38578.peter_e@gmx.net \
--to=peter_e@gmx.net \
--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).