Hi Roman. Branko Čibej wrote: > You can already pin an external to a particular version by adding a -r > parameter to the definition in svn:externals. > > -- Brane > > On 05.05.2011 09:42, muzu...@gmx.net wrote: > > 1. Feature update [--externals MODE] switch: > > > > The update command shall be extended by the following switch and modes: > > > > update [-r rev] [-N] [--externals MODE] > > > > MODE: ignore: > > same as [--ignore-externals] which shall be deprecated but remain for > > backward compatibility > > > > MODE: interactive-revisioned: > > externals set to a fixed revision will not automatically updated to the > > HEAD or the command line revision -r rev but asks per external entry: [yes] > > [no] [yes to all],[no to all] > > > > MODE: ignore-revisioned: > > externals set to a fixed revision will not get updated. Only externals > > working on the head (no –rNNNN entry) will be updated to the HEAD or > > the command line revision –r rev > > > > MODE: to-revision: > > updates externals to the fixed revision stated in the svn:exterals > > property, all others to the HEAD or the command line revison -r rev > > > > MODE: interactive-to-revision: > > updates externals to the fixed revision stated in the svn:exterals > > property, all others to the HEAD or the command line revison -r rev, but > > asks per external entry: [yes] [no] [yes to all],[no to all] [...] > > Motivation/Use-case: > > We want use the svn:externals to retrieve common resources in defined > > versions/revisions into various project. That the resources for the > > particular project keep their revision is very important. They may not > > change by accident. An "standard" update has easily and unwillingly > > happened, as also other user report in the net. If one is lucky the > > compilation fails and one has a indication that sonething is wrong. In the > > worst case everything compiles and works fine, but for a rarely used > > functionality under very unlikely conditions. > > We would like to have update modes that not simple automatically update > > everything to the HEAD or -r rev, but can distingush between "internals", > > externals and revisioned exterals and issue a waring (interactive)
What exactly is wrong with the standard "update" command in your use cases? Are you saying the standard update command ignores the "-r" setting in the externals definitions? In what commands, exactly, and what version of svn? - Julian > > I assume that this is not a server but a pure client feature(?).
