After some digging into this issue - I am somewhat at a loss. I'm not sure
how it happened but I can come up with a best guess that the user may have
checked in the change with 1.6.13 - my suspicion is there is an issue with
how the properties are stored, but unfortunately he has at lease 3
differ
On 06/21/2013 02:22 PM, James Hanley wrote:
> In hind site, if there was a revprop that included the version of the
> client, if an artifact issue (such as this) is discovered in the repository,
> this rev-prop can succinctly tell the administrator which version of the
> client introduced the issue
