[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Checkout through link ignores rev parameter

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 24 Jan 2017 23:19:33 +0100

On Mon, Jan 23, 2017 at 7:54 PM, Dalton, Bill (GE Energy Connections)
<Bill.Dalton_at_ge.com> wrote:
> We have projects which share some of the files in the subversion folders but
> not all. So, those projects put their files into separate folders. One of
> the pairs of folders contains the actual files. The other folder of the
> pair has subversion links which point to the actual files in the other
> folder. This strategy seems to work with only one very important exception.
> When the folder with the links is checked out, the actual files always
> return the HEAD version, ignoring the “rev=” parameter.
> Specifically, there are two folder in Subversion whose paths are
> “trunk/firmware/cpu_fw/dia” and “trunk/firmware/cpu_fw_vx7/dia”. Most of
> the files in the cpu_fw_vx7/dia folder (that is, all of the shared files)
> are links which point to the corresponding file in the cpu_fw/dia folder.
> If the cpu_fw_vx7/dia folder is updated with a “svn update -r 17905
> –non-interactive –force svnRepos/trunk/firmware/cpu_fw_vx7/dia” command, it
> will always fetch the HEAD revision, instead of the 17905 revision.

Hi Bill,

There is no such thing as "Subversion links". I'm assuming you mean
"externals" (more specifically "file externals", if I understand
correctly). Anyway, I think what you're seeing is this bug (which is
very old):

https://issues.apache.org/jira/browse/SVN-2516 (--revision option is
not forwarded to svn:externals references)

The issue was last updated in 2015, with a reference to a mail thread
on the dev-list, containing a design / specs discussion (which
unfortunately seems to have stranded):


Received on 2017-01-24 23:19:58 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.