Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <978EAA10-1E3C-40C3-B6F4-584DD11211B8@ryandesign.com>
References: <BY1P101MB00240F18861E9454F9660D5F8E720@BY1P101MB0024.NAMP101.PROD.OUTLOOK.COM>
 <CAB84uBX-ib-9TXH0UTPC964d01r4tZ2zFHidzK_TdR=Hva7Hrw@mail.gmail.com>
 <CY1P101MB00252D7764F8DB35124A727B8E740@CY1P101MB0025.NAMP101.PROD.OUTLOOK.COM>
 <CAB84uBXoNpOCAVs64Q2UFDJWADr78VszxkT1yt25xgvaPpb3bg@mail.gmail.com>
 <CY1P101MB002576BFA45B79306B54E7788E740@CY1P101MB0025.NAMP101.PROD.OUTLOOK.COM>
 <978EAA10-1E3C-40C3-B6F4-584DD11211B8@ryandesign.com>
From: Johan Corveleyn <jcorvel@gmail.com>
Date: Thu, 26 Jan 2017 18:26:52 +0100
Message-ID: <CAB84uBUG9TeaY_TW+-ww1JebCTB9dRdu7SSAZXL51e+0hcRfJw@mail.gmail.com>
Subject: Re: Checkout through link ignores rev parameter
To: Ryan Schmidt <subversion-2016@ryandesign.com>
Cc: "Dalton, Bill (GE Energy Connections)" <Bill.Dalton@ge.com>, Subversion Users <users@subversion.apache.org>,
	"Hannold, Bill (GE Energy Connections)" <Bill.Hannold@ge.com>,
	"Hawker, Jason (GE Energy Connections)" <jason.hawker@ge.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 26 Jan 2017 17:27:29 -0000

On Wed, Jan 25, 2017 at 9:16 PM, Ryan Schmidt
<subversion-2016@ryandesign.com> wrote:
>
>> On Jan 25, 2017, at 09:59, Dalton, Bill (GE Energy Connections) <Bill.Da=
lton@ge.com> wrote:
>>
>> We know how we would want it to work.  I'm guessing that if we need it "=
fixed", that we would need to get the souce, make our fix, and build our ow=
n version?  That has the advantage of giving us control on how it works for=
 us, but makes updating to future versions complicated and risky.
>
> If you know how to fix a Subversion bug and contribute that fix, I'm sure=
 the Subversion developers would be appreciative.
>

Yes, absolutely. And I think a solution is definitely possible, if
someone is prepared to spend time on it. In this case, I think it's
best to start from that discussion thread from 2015 [1], try to
summarize where it stranded, and bring it up again on the
dev@subversion.apache.org mailinglist with your view on how it should
work. We can then try finding a consensus in the community on the
specs.

Apart from discussing how it should behave (which is the first step),
you might want to take a look at Subversions Community Guide [2].

[1] http://svn.haxx.se/dev/archive-2015-08/0179.shtml
[2] http://subversion.apache.org/docs/community-guide/

--=20
Johan