On Jul 31, 2009, at 12:05, David Weintraub wrote:
> On Thu, Jul 30, 2009 at 7:30 PM, Reagan Penner wrote:
>
>> I am wondering if it is possible to use the start-commit CAPABILITIES
>> feature to block svn client less then 1.6.x?
>
> Well, you'll be able to tell if the client being used has the full
> capabilities of Subversion 1.6, but it won't tell you the version
> of the client.
>
> If you look for "merge-info" capabilities, you'll be able to see
> whether or not the user is using 1.5 or higher. However, revision
> 1.6 doesn't have any more "capabilities" than revision 1.5, so you
> can't use the start-commit hook to see if the client is a 1.6
> version or not.
>
> But, then do you really need to care? There are new capabilities in
> the SVN client side 1.6, but these really don't affect the
> repository when you do a commit. Ther merge tracking capabilities
> in 1.5 and higher do make a difference with the repository which is
> why the whole capabilities thing was added in 1.5. But, the
> capabilities feature doesn't give you the client's actual revision
> number which might not mean much anyway unless the client is using
> the Subversion command line.
There have been a lot of bug fixes in between 1.5.0 and 1.6.3,
including fixes to the merge tracking. It might be nice to ensure
that every client is using a recent enough version that won't
introduce merge tracking errors or other problems that have already
been fixed.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377530
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-31 21:40:00 CEST