Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C827F200C11 for ; Sat, 4 Feb 2017 16:58:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C6A58160B63; Sat, 4 Feb 2017 15:58:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EB47F160B56 for ; Sat, 4 Feb 2017 16:58:16 +0100 (CET) Received: (qmail 4706 invoked by uid 500); 4 Feb 2017 15:58:16 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 4696 invoked by uid 99); 4 Feb 2017 15:58:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Feb 2017 15:58:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6D32D1A05B5 for ; Sat, 4 Feb 2017 15:58:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.679 X-Spam-Level: * X-Spam-Status: No, score=1.679 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 5RDDzEvnMkme for ; Sat, 4 Feb 2017 15:58:14 +0000 (UTC) Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com [209.85.220.173]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id EF2FF5F3BE for ; Sat, 4 Feb 2017 15:58:13 +0000 (UTC) Received: by mail-qk0-f173.google.com with SMTP id u25so18814365qki.2 for ; Sat, 04 Feb 2017 07:58:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=1MtSnPiLnNysQa8rg00iIHo1iCTl1KnxF6BRn7+aA4w=; b=VvBGbn1zwSIsB8er+RJHhi7j6Ko/VEAyeh0T9Rsbc3MKk+fgxv+ExKon4o0D4yvQoW YF89bbY3w992W33Uq8D8KQ+e44fWRv4Mg5/wQ+fOvTz9V0ByFVtmQhPjYXIsmIIEN4Xq M3oNRrijszYBr+Hxlgw0cWQF2uwhE9cDBPl+DZXTF6rX1rtg/PY+djOIKphF6UTpy1fe VC6Eqy7R/o5GOZSHnqacr/oQTrb6wQj/tI4Z4co9twDX2VongI7MepSAqW1H80/G3PXh SiWtF+pRWcTVv8jbKkdbFPeJ+6jdFB6x71qAJ8O+wVFPIdQUnQu4cLeyGnkZGTIvXn3L 7Vzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=1MtSnPiLnNysQa8rg00iIHo1iCTl1KnxF6BRn7+aA4w=; b=JZXZbgwDhlG5ItuD/Rt0Wek9AST75EGRIS3d+jFCCjRkirCynQQI5jjATJ+o3TNjht bjHW2oesZPwdt4U14nxrZWIEm5RbYbOJvgHQa/2el2i1bokZ+RfUCaNnf2tGQX6KhiVW ST8vu1YoKeRX6HefQ09BYdc4kC0WpcdcKV3gmHqWsYCCTZmU3APbcu9LWierg1h3Mrpj ivfcUOx2ustOZ0VZzu+wi5aF3z8okbvoQ1srMZ/YCCAybpXYS/XbpkGLcAlEPoTLoPtZ v2KGu92I+GsNreqaSUF7pa+jETkZ3fK3aE3mWi0+oraBEHeXElfuwTWccrQitNECcF6C o/vw== X-Gm-Message-State: AMke39n2X/hncVz9AbfvZBMUwgjImZk7p7O+2+0p7EuDCY7NmfU34mZ9SJs2E8MvUDNMjTd2iNMAhL1NldIkdg== X-Received: by 10.55.0.148 with SMTP id t20mr2182070qkg.299.1486223885566; Sat, 04 Feb 2017 07:58:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.129.72 with HTTP; Sat, 4 Feb 2017 07:57:45 -0800 (PST) In-Reply-To: <6a1d3ef8-8888-5ca4-f036-f33fa4c078c7@gmail.com> References: <68b74702-0be0-c402-3fce-982713dc8676@gmail.com> <20170204101615.n52atjsucsqlqpdg@jim.stsp.name> <20170204131245.b52zx5nzpe6wvntv@jim.stsp.name> <6a1d3ef8-8888-5ca4-f036-f33fa4c078c7@gmail.com> From: =?UTF-8?B?U3RlZmFuIEvDvG5n?= Date: Sat, 4 Feb 2017 16:57:45 +0100 Message-ID: Subject: Re: wish for new API or extended one To: Subversion Development Content-Type: multipart/alternative; boundary=001a11455678c18c5f0547b676ef archived-at: Sat, 04 Feb 2017 15:58:18 -0000 --001a11455678c18c5f0547b676ef Content-Type: text/plain; charset=UTF-8 On Sat, Feb 4, 2017 at 4:41 PM, Stefan Kueng wrote: > > > On 04.02.2017 14:12, Stefan Sperling wrote: > >> On Sat, Feb 04, 2017 at 01:45:10PM +0100, Stefan Kueng wrote: >> >>> On 04.02.2017 11:16, Stefan Sperling wrote: >>> >>>> On Sat, Feb 04, 2017 at 09:23:06AM +0100, Stefan Kueng wrote: >>>> >>>>> Hi, >>>>> >>>>> while trying out the new conflict resolver APIs I came upon a slight >>>>> problem. The API svn_client_conflict_option_get_description() returns >>>>> a >>>>> string that can be used to show to the user as a choice - in TSVN that >>>>> would >>>>> be the text on a two-line button (the 'label' is the first line, the >>>>> 'description' the second line). >>>>> >>>>> The problem I'm having now is that the description is always the same, >>>>> even >>>>> if there are multiple 'moved-to-candidates' available. And if we use >>>>> another >>>>> than the first moved-to-candidate, the description mentions the wrong >>>>> path. >>>>> >>>> >>>> So you're calling svn_client_conflict_option_set >>>> _moved_to_repos_relpath() >>>> and if you then get the description again the path isn't updated? >>>> That would be a bug. >>>> >>> > So I tried exactly that, and for me the description is not updated. It > returns the same description no matter what move path index I set: the > description always mentions the first path. > > But fetching the path with > const char * p = APR_ARRAY_IDX(possible_moved_to_repos_relpaths, j, const > char *); > shows a different path. > > Another thing that confuses me: > After calling get_details(), the description mentions which path is the > reason for the conflict. So why does svn_client_conflict_option_get > _moved_to_repos_relpath_candidates still get me a list of paths to chose > from if the path is already known? > I'm a little bit confused... > Sorry, confusion fixed. After going through the code a little bit I now understand why. But the problem with the description not being updated still persists. Stefan -- ___ oo // \\ "De Chelonian Mobile" (_,\/ \_/ \ TortoiseSVN \ \_/_\_/> The coolest Interface to (Sub)Version Control /_/ \_\ http://tortoisesvn.net --001a11455678c18c5f0547b676ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sat, Feb 4, 2017 at 4:41 PM, Stefan Kueng <tortoisesvn@gmail.co= m> wrote:
=

On 04.02.2017 14:12, Stefan Sperling wrote:
On Sat, Feb 04, 2017 at 01:45:10PM +0100, Stefan Kueng wrote:
On 04.02.2017 11:16, Stefan Sperling wrote:
On Sat, Feb 04, 2017 at 09:23:06AM +0100, Stefan Kueng wrote:
Hi,

while trying out the new conflict resolver APIs I came upon a slight
problem. The API svn_client_conflict_option_get_description() returns = a
string that can be used to show to the user as a choice - in TSVN that woul= d
be the text on a two-line button (the 'label' is the first line, th= e
'description' the second line).

The problem I'm having now is that the description is always the same, = even
if there are multiple 'moved-to-candidates' available. And if we us= e another
than the first moved-to-candidate, the description mentions the wrong path.=

So you're calling svn_client_conflict_option_set_moved_to_repos_re= lpath()
and if you then get the description again the path isn't updated?
That would be a bug.

So I tried exactly that, and for me the description is not updated. It retu= rns the same description no matter what move path index I set: the descript= ion always mentions the first path.

But fetching the path with
const char * p =3D APR_ARRAY_IDX(possible_moved_to_repos_relpaths, j, = const char *);
shows a different path.

Another thing that confuses me:
After calling get_details(), the description mentions which path is the rea= son for the conflict. So why does svn_client_conflict_option_get_moved= _to_repos_relpath_candidates still get me a list of paths to chose fro= m if the path is already known?
I'm a little bit confused...

Sorry, confusion fixed. After= going through the code a little bit I now understand why.

But the problem with the description not being updated still persists.
Stefan

--
=C2=A0 =C2=A0 =C2= =A0=C2=A0 ___
=C2=A0 oo=C2=A0 // \\=C2=A0 =C2=A0 =C2=A0 "De Cheloni= an Mobile"
=C2=A0(_,\/ \_/ \=C2=A0 =C2=A0=C2=A0 TortoiseSVN
=C2= =A0=C2=A0 \ \_/_\_/>=C2=A0 =C2=A0 The coolest Interface to (Sub)Version = Control
=C2=A0=C2=A0 /_/=C2=A0=C2=A0 \_\=C2=A0 =C2=A0=C2=A0 http://tortoisesvn.net
--001a11455678c18c5f0547b676ef--