All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Obry <pascal@obry.net>
To: Avery Pennarun <apenwarr@gmail.com>,
	Eric Wong <normalperson@yhbt.net>,
	adambrewster@gmail.com
Cc: git list <git@vger.kernel.org>
Subject: Re: git-svn problem with v1.6.5
Date: Wed, 11 Nov 2009 11:28:11 +0100	[thread overview]
Message-ID: <4AFA91BB.7050402@obry.net> (raw)
In-Reply-To: <32541b130911101428t50038cfcsf37e3ea9edb26f64@mail.gmail.com>


Avery,

 > Is d2cf08bb67e4b7da33a250127aab784f1f2f58d3 a valid revision?  (git
 > log d2cf08bb67e4b7da33a250127aab784f1f2f58d3).

No.

 > Is refs/remotes/svn/trunk valid?  (git log refs/remotes/svn/trunk).

Yes.

 > It seems like a strange problem.

Agreed!

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

I wanted to avoid that :) Anyway, here is the culprit:


commit 6f5748e14cc5bb0a836b649fb8e2d6a5eb166f1d
Author: Adam Brewster <adambrewster@gmail.com>
Date:   Tue Aug 11 23:14:27 2009 -0400

     svn: allow branches outside of refs/remotes

     It may be convenient for some users to store svn remote tracking
     branches outside of the refs/remotes/ heirarchy.

     To accomplish this feat, this patch includes the entire path to
     the ref in $r->{'refname'} in &read_all_remotes and tries to change
     references to this entry so the new value makes sense.

     [ew: fixed backwards compatibility, long lines]

     Signed-off-by: Adam Brewster <adambrewster@gmail.com>
     Signed-off-by: Eric Wong <normalperson@yhbt.net>

  git-svn.perl                     |   83 
++++++++++++++++++++++----------------
  t/lib-git-svn.sh                 |    2 +-
  t/t9104-git-svn-follow-parent.sh |   10 ++--
  t/t9107-git-svn-migrate.sh       |   14 +++----
  t/t9143-git-svn-gc.sh            |   10 ++--
  t/t9144-git-svn-old-rev_map.sh   |   31 ++++++++++++++
  6 files changed, 96 insertions(+), 54 deletions(-)


But frankly I'm no expert on Perl... I fear that I won't be able to 
debug that!

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B

  reply	other threads:[~2009-11-11 10:28 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
2009-11-11 10:28   ` Pascal Obry [this message]
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=4AFA91BB.7050402@obry.net \
    --to=pascal@obry.net \
    --cc=adambrewster@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.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 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.