Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
From: "Dalton, Bill (GE Energy Connections)" <Bill.Dalton@ge.com>
To: "users@subversion.apache.org" <users@subversion.apache.org>
CC: "Hannold, Bill (GE Energy Connections)" <Bill.Hannold@ge.com>
Subject: Checkout through link ignores rev parameter
Thread-Topic: Checkout through link ignores rev parameter
Thread-Index: AdJ1qA4Iex25o/w+RZepldEwCcSATQ==
Date: Mon, 23 Jan 2017 18:54:07 +0000
Message-ID: <BY1P101MB00240F18861E9454F9660D5F8E720@BY1P101MB0024.NAMP101.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: ge.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_BY1P101MB00240F18861E9454F9660D5F8E720BY1P101MB0024NAMP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2017 18:54:07.2169
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 15ccb6d1-d335-4996-b6f9-7b6925f08121
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1P101MB0183
X-OriginatorOrg: ge.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-01-23_15:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0
 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam
 adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000
 definitions=main-1701230246
archived-at: Tue, 24 Jan 2017 12:51:58 -0000

--_000_BY1P101MB00240F18861E9454F9660D5F8E720BY1P101MB0024NAMP_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We have projects which share some of the files in the subversion folders bu=
t 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 fol=
der.  This strategy seems to work with only one very important exception.  =
When  the folder with the links is checked out, the actual files always ret=
urn the HEAD version, ignoring the "rev=3D" parameter.

Specifically, there are two folder in Subversion whose paths are "trunk/fir=
mware/cpu_fw/dia" and "trunk/firmware/cpu_fw_vx7/dia".  Most of the files i=
n the cpu_fw_vx7/dia folder (that is, all of the shared files) are links wh=
ich point to the corresponding file in the cpu_fw/dia folder.  If the cpu_f=
w_vx7/dia folder is updated with a "svn update -r 17905 -non-interactive -f=
orce svnRepos/trunk/firmware/cpu_fw_vx7/dia" command, it will always fetch =
the HEAD revision, instead of the 17905 revision.


--_000_BY1P101MB00240F18861E9454F9660D5F8E720BY1P101MB0024NAMP_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">We have projects which share some of the files in th=
e subversion folders but not all.&nbsp; So, those projects put their files =
into separate folders.&nbsp; One of the pairs of folders contains the actua=
l files.&nbsp; The other folder of the pair has subversion
 links which point to the actual files in the other folder.&nbsp; This stra=
tegy seems to work with only one very important exception.&nbsp; When &nbsp=
;the folder with the links is checked out, the actual files always return t=
he HEAD version, ignoring the &#8220;rev=3D&#8221; parameter.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Specifically, there are two folder in Subversion who=
se paths are &#8220;trunk/firmware/cpu_fw/dia&#8221; and &#8220;trunk/firmw=
are/cpu_fw_vx7/dia&#8221;.&nbsp; Most of the files in the cpu_fw_vx7/dia fo=
lder (that is, all of the shared files) are links which point to
 the corresponding file in the cpu_fw/dia folder.&nbsp; If the cpu_fw_vx7/d=
ia folder is updated with a &#8220;svn update -r 17905 &#8211;non-interacti=
ve &#8211;force svnRepos/trunk/firmware/cpu_fw_vx7/dia&#8221; command, it w=
ill always fetch the HEAD revision, instead of the 17905 revision.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_BY1P101MB00240F18861E9454F9660D5F8E720BY1P101MB0024NAMP_--