[
https://issues.apache.org/jira/browse/SVN-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-2516:
-----------------------------
Description:
When you do 'svn up -rN' or 'svn export -rN', svn:externals underneath do not
respond to the -rN, even if the {{svn:externals}} values do not have specific
-r values themselves. We could detect when the externals are from the same
repository as the primary target of the update and have the externals use the
same revision. There would be a compatibility issue, but note that the
workaround is simply to explicitly pass -rHEAD in the externals description,
since -rHEAD is the default behavior
right now.
This mail describes the problem and provides a script to demonstrate it:
{quote}
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=45802
From: j...@jmason.org (Justin Mason)
To: us...@subversion.tigris.org
Cc: d...@spamassassin.apache.org
Subject: iffy behaviour with SVN external and "svn up -r"
Date: Wed, 01 Mar 2006 12:00:55 +0000
Message-Id: <20060301120055.2236d590...@radish.jmason.org>
{quote}
See comments in issue SVN-2209 about some of the infrastructure needed to
implement this enhancement.
was:
{noformat:nopanel=true}
When you do 'svn up -rN' or 'svn export -rN', svn:externals underneath
do not respond to the -rN, even if the svn:externals values do not
have specific -r values themselves. We could detect when the externals
are from the same repository as the primary target of the update and
have the externals use the same revision. There would be a compatibility
issue, but note that the workaround is simply to explicitly pass -rHEAD
in the externals description, since -rHEAD is the default behavior
right now.
This mail describes the problem and provides a script to demonstrate it:
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=45802
From: j...@jmason.org (Justin Mason)
To: us...@subversion.tigris.org
Cc: d...@spamassassin.apache.org
Subject: iffy behaviour with SVN external and "svn up -r"
Date: Wed, 01 Mar 2006 12:00:55 +0000
Message-Id: <20060301120055.2236d590...@radish.jmason.org>
See comments in issue #2209 about some of the infrastructure needed to
implement this enhancement.
{noformat}
> --revision option is not forwarded to svn:externals references
> --------------------------------------------------------------
>
> Key: SVN-2516
> URL: https://issues.apache.org/jira/browse/SVN-2516
> Project: Subversion
> Issue Type: Improvement
> Components: libsvn_wc
> Affects Versions: trunk
> Reporter: Karl Fogel
> Fix For: unscheduled
>
>
> When you do 'svn up -rN' or 'svn export -rN', svn:externals underneath do not
> respond to the -rN, even if the {{svn:externals}} values do not have specific
> -r values themselves. We could detect when the externals are from the same
> repository as the primary target of the update and have the externals use the
> same revision. There would be a compatibility issue, but note that the
> workaround is simply to explicitly pass -rHEAD in the externals description,
> since -rHEAD is the default behavior
> right now.
> This mail describes the problem and provides a script to demonstrate it:
> {quote}
> http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=45802
> From: j...@jmason.org (Justin Mason)
> To: us...@subversion.tigris.org
> Cc: d...@spamassassin.apache.org
> Subject: iffy behaviour with SVN external and "svn up -r"
> Date: Wed, 01 Mar 2006 12:00:55 +0000
> Message-Id: <20060301120055.2236d590...@radish.jmason.org>
> {quote}
> See comments in issue SVN-2209 about some of the infrastructure needed to
> implement this enhancement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
