A single argument specifying a revision may only work for very specific
scenarios. The --pin-externals feature also works when you have dozens of
externals, all pointing towards different repositories.
When adding the feature we determined that we can't handle all these
additional cases using the generic copy api. This function really 'pins'
what a checkout would do at the time of the pinning. going any further would
require much manual work from the user, which he/she could already do before
we added this. (Update working copy manually, and commit by using svn cp
PATH URL. Perhaps revert the local copy after this)
Bert
From: Israel Sadeh [mailto:israel.sa...@rtc-vision.com]
Sent: donderdag 1 september 2016 18:47
To: users@subversion.apache.org
Subject: SVN Feature Request: Selecting the revision for pinning externals
Hi,
The new '-pin-externals' switch of the 'svn copy' command pins the externals
to their latest version.
This makes sense when copying the latest revision, but in case the copied
branch is from an older revision, it also makes sense to pin the externals
to the old revision.
This way in case it will be possible to create a tag from an old revision,
and not only from the latest one.
My suggestion: Add an optional pinning-revision parameter to the
'-pin-externals' switch.
By default (if the pinning-revision' parameter isn't set) - the externals
will be pinned to the latest version.
If the parameter is set - the externals will be pinned to the parameter
revision.
Best regards,
Israel Sadeh
Israel Sadeh
Software Engineer
RTC Vision Ltd.
<http://www.rtc-vision.com/> www.rtc-vision.com
