git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Peter Eisentraut" <peter_e@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: cvsimport infinite loop
Date: Sun, 10 Feb 2008 01:01:43 +1300	[thread overview]
Message-ID: <46a038f90802090401n431659a5p1a9b457d4338695d@mail.gmail.com> (raw)
In-Reply-To: <200802091245.38578.peter_e@gmx.net>

On Feb 10, 2008 12:45 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> 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.

Might be a bug in cvsps -- I tried an import earlier this year of the
Pg repo and had a similar problem. parsecvs did handle it, but cannot
do incrementals, which is a real shame.

cheers.


m

  reply	other threads:[~2008-02-09 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 11:45 cvsimport infinite loop Peter Eisentraut
2008-02-09 12:01 ` Martin Langhoff [this message]
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=46a038f90802090401n431659a5p1a9b457d4338695d@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peter_e@gmx.net \
    /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).