Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <CA+298UjaLbKwa7RzT7Tr5THDp1AVtEJoiY=JVS7rYdGHdtQQzg@mail.gmail.com>
References: <CA+298UjaLbKwa7RzT7Tr5THDp1AVtEJoiY=JVS7rYdGHdtQQzg@mail.gmail.com>
Date: Sat, 11 Jun 2016 16:37:16 +0200
Message-ID: <CAB84uBU4mhzqEczNkRAXsN79bd=K6bqYhqWT-v+uRZ5bcwogyg@mail.gmail.com>
Subject: Re: SVN-4635: Cherry-pick merge scenario causes Svn to choke
From: Johan Corveleyn <jcorvel@gmail.com>
To: Paul Hammant <paul@hammant.org>
Cc: Subversion Development <dev@subversion.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c07df1e87437505350197b4
archived-at: Sat, 11 Jun 2016 14:37:22 -0000

--94eb2c07df1e87437505350197b4
Content-Type: text/plain; charset=UTF-8

Op 11-jun.-2016 12:37 schreef "Paul Hammant" <paul@hammant.org>:
>
> http://subversion.apache.org/docs/community-guide/issues.html amongst
other things, says "
> if you're pretty sure about the bug, go ahead and post directly to our
development list". OK, so here's a bug with merge tracking:
>
>    https://issues.apache.org/jira/browse/SVN-4635
>
>    Synopsis: Series of cherry-picks between branches breaks subversions
merge tracking
>
> A reproducible bug, I should say - there's bash scripts within the issue.
made on a mac and tested with Svn 1.9.4.
>
> I even ported the same scripts to Perforce, Git and Mercurial (same
sequence of merge events) and it
> works fine. The code for those is on branches in that same Git repo.
>

Hi Paul,

Thank you for reporting this issue, with reproduction script and all.

It's fine that you try to draw a little attention to it with your post to
dev@. However, at this time resources are quite low in our little dev
community, so I'm not sure when someone will be able to take a closer look.

Patches are always welcome of course :-), but I know that not everyone has
the time to go that route ...

Regardless, thanks for the issue report.

-- 
Johan

--94eb2c07df1e87437505350197b4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Op 11-jun.-2016 12:37 schreef &quot;Paul Hammant&quot; &lt;<=
a href=3D"mailto:paul@hammant.org">paul@hammant.org</a>&gt;:<br>
&gt;<br>
&gt; <a href=3D"http://subversion.apache.org/docs/community-guide/issues.ht=
ml">http://subversion.apache.org/docs/community-guide/issues.html</a> among=
st other things, says &quot;<br>
&gt; if you&#39;re pretty sure about the bug, go ahead and post directly to=
 our development list&quot;. OK, so here&#39;s a bug with merge tracking:<b=
r>
&gt;<br>
&gt; =C2=A0 =C2=A0<a href=3D"https://issues.apache.org/jira/browse/SVN-4635=
">https://issues.apache.org/jira/browse/SVN-4635</a><br>
&gt;<br>
&gt; =C2=A0 =C2=A0Synopsis: Series of cherry-picks between branches breaks =
subversions merge tracking<br>
&gt;<br>
&gt; A reproducible bug, I should say - there&#39;s bash scripts within the=
 issue. made on a mac and tested with Svn 1.9.4.<br>
&gt;<br>
&gt; I even ported the same scripts to Perforce, Git and Mercurial (same se=
quence of merge events) and it <br>
&gt; works fine. The code for those is on branches in that same Git repo. <=
br>
&gt;</p>
<p dir=3D"ltr">Hi Paul,</p>
<p dir=3D"ltr">Thank you for reporting this issue, with reproduction script=
 and all.</p>
<p dir=3D"ltr">It&#39;s fine that you try to draw a little attention to it =
with your post to dev@. However, at this time resources are quite low in ou=
r little dev community, so I&#39;m not sure when someone will be able to ta=
ke a closer look.</p>
<p dir=3D"ltr">Patches are always welcome of course :-), but I know that no=
t everyone has the time to go that route ...</p>
<p dir=3D"ltr">Regardless, thanks for the issue report.</p>
<p dir=3D"ltr">-- <br>
Johan </p>

--94eb2c07df1e87437505350197b4--