git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* git-svn fetch hangs or gives broken pipe on a specific "branch"
@ 2007-06-05 16:53 Bill Priest
  2007-06-06  8:27 ` Eric Wong
  0 siblings, 1 reply; 2+ messages in thread
From: Bill Priest @ 2007-06-05 16:53 UTC (permalink / raw)
  To: git

All,
  I'm trying to use git to try out its merging
capabilities as I'm not "happy" w/ what svn provides. 
From Linus discussion at google (from YouTube) he
indicated that many people use it to manage merges
between branches and then push back into the
subversion repository.  I'd like to do this as
converting to git from svn (less than 6 months after
converting from cvs to svn isn't an easy sell to
management).
  We have a small team (~5 developers) and a fairly
small project (a few hundred files).  From a web
site/wiki I found the following instructions (tweaked
for my setup).
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?

TIA,

Bill



       
____________________________________________________________________________________
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
http://new.toolbar.yahoo.com/toolbar/features/mail/index.php

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: git-svn fetch hangs or gives broken pipe on a specific "branch"
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2007-06-06  8:27 UTC (permalink / raw)
  To: Bill Priest; +Cc: git

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-06-06  8:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).