From: "Jan Pešta" <jan.pesta@certicon.cz>
To: "'Matthieu Moy'" <Matthieu.Moy@grenoble-inp.fr>
Cc: <git@vger.kernel.org>
Subject: RE: [PATCH] GIT SVN
Date: Fri, 1 Mar 2013 13:55:32 +0100 [thread overview]
Message-ID: <001001ce167c$0f376f10$2da64d30$@certicon.cz> (raw)
In-Reply-To: <vpqsj4fmhgu.fsf@grenoble-inp.fr>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
Hi again,
Finally I created patch according to document.
Please have a look on referenced site for more details.
Currently I have a problems in our project, where SVN is main repository and
merge-info contains "*" which causes troubles in SVN.pm.
Regards,
Jan
Kind regards / S pozdravem
Jan Pešta
SW Engineer Sr.
CertiCon a.s., www.certicon.cz
Vaclavska 12
12000 Prague 2
Czech Republic
Office Prague: +420 224 904 406
Mobile: +420 604 794 306
E-mail: jan.pesta@certicon.cz
-----Original Message-----
From: Matthieu Moy [mailto:Matthieu.Moy@grenoble-inp.fr]
Sent: Friday, March 01, 2013 1:29 PM
To: Jan Pešta
Cc: git@vger.kernel.org
Subject: Re: [PATCH] GIT SVN
Jan Pešta <jan.pesta@certicon.cz> writes:
> Sorry,
> My fault :)
>
> Here is a patch atached.
Still, please, read Documentation/SubmittingPatches. Your patch cannot be
included as it is because of lack of sign-off.
Also, please write a commit message describing why this change is needed.
Where is this extra "*" comming from, and why do you need to remove it?
Thanks,
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
[-- Attachment #2: 0001-In-inproperly-merges-the-ranges-contains-additional-.patch --]
[-- Type: application/octet-stream, Size: 1089 bytes --]
>From 03aefff110cc46a82e87c01fed38ac6bb22b353b Mon Sep 17 00:00:00 2001
From: Jan Pesta <jan.pesta@certicon.cz>
Date: Fri, 1 Mar 2013 10:30:42 +0100
Subject: [PATCH] In inproperly merges, the ranges contains additional
character "*".
See http://www.open.collab.net/community/subversion/articles/merge-info.html
Extract:
The range r30430:30435 that was added to 1.5.x in this merge has a '*' suffix for 1.5.x\www.
This '*' is the marker for a non-inheritable mergeinfo range.
The '*' means that only the path on which the mergeinfo is explicitly set has had this range merged into it.
---
perl/Git/SVN.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/perl/Git/SVN.pm b/perl/Git/SVN.pm
index 0ebc68a..6bd18e9 100644
--- a/perl/Git/SVN.pm
+++ b/perl/Git/SVN.pm
@@ -1493,6 +1493,7 @@ sub lookup_svn_merge {
my @merged_commit_ranges;
# find the tip
for my $range ( @ranges ) {
+ $range =~ s/[*]$//;
my ($bottom, $top) = split "-", $range;
$top ||= $bottom;
my $bottom_commit = $gs->find_rev_after( $bottom, 1, $top );
--
1.8.1.msysgit.1
next prev parent reply other threads:[~2013-03-01 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 12:24 [PATCH] GIT SVN Jan Pešta
2013-03-01 12:29 ` Matthieu Moy
2013-03-01 12:55 ` Jan Pešta [this message]
2013-03-01 13:07 ` Matthieu Moy
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='001001ce167c$0f376f10$2da64d30$@certicon.cz' \
--to=jan.pesta@certicon.cz \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/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