git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: pascal@obry.net
Cc: git list <git@vger.kernel.org>
Subject: Re: git-svn problem with v1.6.5
Date: Tue, 10 Nov 2009 17:28:39 -0500	[thread overview]
Message-ID: <32541b130911101428t50038cfcsf37e3ea9edb26f64@mail.gmail.com> (raw)
In-Reply-To: <4AF9E7FE.3060701@obry.net>

On Tue, Nov 10, 2009 at 5:23 PM, Pascal Obry <pascal@obry.net> wrote:
> $ git svn rebase
> fatal: Invalid revision range
> d2cf08bb67e4b7da33a250127aab784f1f2f58d3..refs/remotes/svn/trunk
> rev-list --pretty=raw --no-color --reverse
> d2cf08bb67e4b7da33a250127aab784f1f2f58d3..refs/remotes/svn/trunk --: command
> returned error: 128

Is d2cf08bb67e4b7da33a250127aab784f1f2f58d3 a valid revision?  (git
log d2cf08bb67e4b7da33a250127aab784f1f2f58d3).  Is
refs/remotes/svn/trunk valid?  (git log refs/remotes/svn/trunk).  It
seems like a strange problem.

> Using v1.6.4 instead I have no problem. Any idea to track this problem down?

You could try using git bisect to figure out which exact commit to
git.git created the problem.

Avery

  reply	other threads:[~2009-11-10 22:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 22:23 git-svn problem with v1.6.5 Pascal Obry
2009-11-10 22:28 ` Avery Pennarun [this message]
2009-11-11 10:28   ` Pascal Obry
2009-11-11 19:41     ` Avery Pennarun
2009-11-11 19:58       ` Pascal Obry
2009-11-11 20:22         ` Eric Wong
2009-11-11 20:34           ` Eric Wong
2009-11-11 21:55             ` Pascal Obry
2009-11-11 22:44               ` Eric Wong
2009-11-12  6:39                 ` Pascal Obry
2009-11-12  7:11                   ` Eric Wong
2009-11-12  8:11                     ` Pascal Obry
2009-11-12  9:03                       ` Pascal Obry
2009-11-12  9:35                         ` Eric Wong
2009-11-12 10:00                           ` Pascal Obry
2009-11-11  4:02 ` Sam Vilain
2009-11-11  8:11   ` Pascal Obry

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=32541b130911101428t50038cfcsf37e3ea9edb26f64@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pascal@obry.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).