git-svn: establish new connections on commit after fork
SVN seems to have a problem with https:// repositories from time-to-time when doing multiple, sequential commits. This problem is not consistently reproducible without the patch, but it should go away entirely with this patch... Signed-off-by: Eric Wong <normalperson@yhbt.net> Signed-off-by: Junio C Hamano <junkio@cox.net>
Eric Wong committed
Aug 25, 2006 at 12:28 UTC
5a990e45f920b50aa6b81823120223fb50f56d97
1 file changed
+4
git-svn.perl
+4
@@ -500,6 +500,8 @@ sub commit_lib {
500
my @lock = $SVN::Core::VERSION ge '1.2.0' ? (undef, 0) : ();
501
my $commit_msg = "$GIT_SVN_DIR/.svn-commit.tmp.$$";
502
503
+ my $repo;
504
+ ($repo, $SVN_PATH) = repo_path_split($SVN_URL);
505
set_svn_commit_env();
506
foreach my $c (@revs) {
507
my $log_msg = get_commit_message($c, $commit_msg);
@@ -508,6 +510,8 @@ sub commit_lib {
510
# can't track down... (it's probably in the SVN code)
511
defined(my $pid = open my $fh, '-|') or croak $!;
512
if (!$pid) {
513
+ $SVN_LOG = libsvn_connect($repo);
514
+ $SVN = libsvn_connect($repo);
515
my $ed = SVN::Git::Editor->new(
516
{ r => $r_last,
517
ra => $SVN,