From: Sam Vilain <sam@vilain.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Harvey Harrison <harvey.harrison@gmail.com>
Subject: Re: [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping
Date: Thu, 13 Dec 2007 15:42:01 +1300 [thread overview]
Message-ID: <47609BF9.4030005@vilain.net> (raw)
In-Reply-To: <20071212180510.GB18980@untitled>
Eric Wong wrote:
> Sam (or anybody else using useSvmProps:
>
> Do you have any feedback with svmProps enabled?
3682645 120 -rw-rw-r-- 1 samv samv 121893 Dec 13 14:05
tags/debian_version_1_2_0beta1@2972/.rev_db.d29f7b36-84ff-0310-85ce-ba787dbd31ca
=>
-3683050 4 -rw-rw-r-- 1 samv samv 48 Dec 13 14:26
./tags/debian_version_1_2_0beta1@2972/.rev_map.d29f7b36-84ff-0310-85ce-ba787dbd31ca
git-log --all | grep git-svn | tail -3
git-svn-id:
file:///home/samv/.svk/local/mirror/fai/branches/source-dist@2971
d29f7b36-84ff-0310-85ce-ba787dbd31ca
git-svn-id: svn+ssh://svn.debian.org/svn/fai/trunk@2
ba5ec265-b0fb-0310-8e1a-cf9e4c2b1591
git-svn-id: svn+ssh://svn.debian.org/svn/fai/trunk@1
ba5ec265-b0fb-0310-8e1a-cf9e4c2b1591
So, the remapping is still working fine.
The one that failed there is not a new bug. Here's the fix anyway
though :-)
Subject: [PATCH] git-svn: fix --use-svm-props and --follow-parent
If, when using --follow-parent, it finds that the parent is an SVM
path, *and* the SVM path is not at the root of the corresponding SVN
repository (the usual case when using SVK), then the logic in
Git::SVN::ra will not find the correct source repository. This is
because the freshly created RA object is missing the path. So, set
this after creation.
Signed-off-by: Sam Vilain <sam.vilain@catalyst.net.nz>
---
git-svn.perl | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index 54d7844..3e5fd82 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -2189,6 +2189,7 @@ sub find_parent_branch {
$ref_id .= '-' while find_ref($ref_id);
print STDERR "Initializing parent: $ref_id\n";
$gs = Git::SVN->init($new_url, '', $ref_id, $ref_id, 1);
+ $gs->{path} = $branch_from;
}
my ($r0, $parent) = $gs->find_rev_before($r, 1);
if (!defined $r0 || !defined $parent) {
--
1.5.3.5
next prev parent reply other threads:[~2007-12-13 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 7:27 [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping Eric Wong
2007-12-09 7:27 ` [PATCH 1/2] git-svn: replace .rev_db with a more space-efficient .rev_map format Eric Wong
2007-12-09 7:27 ` [PATCH 2/2] git-svn: reinstate old rev_db optimization in new rev_map Eric Wong
2007-12-09 20:56 ` [PATCH 0/2] [RFT] git-svn: more efficient revision -> commit mapping Harvey Harrison
2007-12-10 1:04 ` Harvey Harrison
2007-12-12 18:05 ` Eric Wong
2007-12-13 2:42 ` Sam Vilain [this message]
2007-12-13 16:30 ` Eric Wong
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=47609BF9.4030005@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=harvey.harrison@gmail.com \
--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.