Oliver Zeigermann wrote:
Martin Holz wrote:
Oliver Zeigermann <[EMAIL PROTECTED]> writes:
Please have a look at this very simple patch. I have set the display name of the VHR to the displayname of the resource that gets versioned. This makes it easier to find the versions of the resource in the history folder with non-DeltaV-aware clients like the Windows Explorer as they are no longer called '4711', but rahter 'Important.doc'. Please note that this does not effect the path of the VHR, but only the displayname.
What happens, if there is a branch and displaynames in both branches are different? Whatever is checked in later wins?
Yes. My tiny patch is only to be considered a hint for the small scale user. He/she may have only a few files flying around and no DeltaV-aware client. The displayname is merely a hint to have a reference to where versiones can be found. It is also less effective if we enable your patch for smaller collection sizes as only the last part of the path will be named after the resource.
I just though it does not do any harm in large scale scenarios, but may be useful in small scale ones.
Ah sorry, the answer is 'no'. The displayname is set upon creation of the VHR, so it is set as soon as the resource is put under version control.
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
