From: Eric Wong <normalperson@yhbt.net>
To: Bill Priest <priestwilliaml@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn fetch hangs or gives broken pipe on a specific "branch"
Date: Wed, 6 Jun 2007 01:27:28 -0700 [thread overview]
Message-ID: <20070606082728.GA16321@muzzle> (raw)
In-Reply-To: <689181.83891.qm@web55015.mail.re4.yahoo.com>
Bill Priest <priestwilliaml@yahoo.com> wrote:
> I downloaded the latest release of git 1.5.2 and built
> it on RHEL box. Subversion version is 1.4.2. The
> repository and the git working directory are on the
> same machine (taking networking out of the picture).
> mkdir git_test
> cd git_test
> git-svn init -t tags -b branches -T trunk "my URL"
> Initialized empty Git repository in .git/
> git-svn fetch
> all tags were processed w/o error AFAICT; the first
> branch it tries to work on causes either a hang or a
> "Broken Pipe". I changed from an http:// to svn:// on
> the git-svn init and everything worked correctly.
> This would seem to indicate some type of problem w/
> apache/httpd problem. I looked in the httpd logs and
> didn't see any errors.
> Is this a known problem?
No. Is it reproducible? In my experience, http(s):// has been much
less problematic than svn:// repositories (because I mainly access
https:// ones).
Also, are you certain the git-svn you're running is 1.5.2? When you
say that it processed all tags before hitting a branch, that
sounds like the behavior of a pre-1.5.1 git-svn. Run git-svn --version
just to be sure :)
git-svn 1.5.1+ fetches trunk, tags, and branches in chronological order.
Of course, your project may have never created a branch before any of
your tags are created...
Any details on the branch that caused it to fail would be appreciated,
thanks.
--
Eric Wong
prev parent reply other threads:[~2007-06-06 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 16:53 git-svn fetch hangs or gives broken pipe on a specific "branch" Bill Priest
2007-06-06 8:27 ` Eric Wong [this message]
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=20070606082728.GA16321@muzzle \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=priestwilliaml@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.