git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benson Margulies <bimargulies@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: On MacOS, 1.7.2, git svn clone seems to fail silently
Date: Fri, 30 Jul 2010 21:34:54 -0400	[thread overview]
Message-ID: <AANLkTim4T2NtRpyWfi8_8AVNYmVSqSsTnoA7fj69K-FA@mail.gmail.com> (raw)
In-Reply-To: <20100731011332.GE5817@burratino>

On Fri, Jul 30, 2010 at 9:13 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi Benson,
>
> Benson Margulies wrote:
>> git svn clone -s https://gate.svn.sourceforge.net/svnroot/gate
> [...]
>> No errors, no messages. No branches, no contents. Just the
>> wind whistling through the bytes.

 I don't have $? at hand, but I can tell you that git branch -r says
 nothing, either. Also, running git fetch has the same result. Prints
 the same sort of trace lines if tracing, then does nothing

>
> Heh - you might be the one to figure out
> http://thread.gmane.org/gmane.comp.version-control.git/134936
>
> But first, it would be good to confirm:
>
>  - if you run "echo $?" right after such a failure, what
>   status code do you get?
>
>  - what is the output of "git branch -r" when you finish?
>
> Coping strategy: usually with "git svn clone" failures, you can resume
> where you left off with "git svn fetch".
>
> Good luck,
> Jonathan
>

  reply	other threads:[~2010-07-31  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31  1:05 On MacOS, 1.7.2, git svn clone seems to fail silently Benson Margulies
2010-07-31  1:13 ` Jonathan Nieder
2010-07-31  1:34   ` Benson Margulies [this message]
2010-07-31  1:35 ` Jonathan Nieder
2010-07-31  1:40   ` Benson Margulies
2010-07-31  2:28   ` Benson Margulies
2010-07-31  2:30     ` Bryan Donlan
2010-07-31  2:32     ` Benson Margulies

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=AANLkTim4T2NtRpyWfi8_8AVNYmVSqSsTnoA7fj69K-FA@mail.gmail.com \
    --to=bimargulies@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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 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).