[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: merge tracking: rejecting commits from svn clients < 1.5

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2007-02-17 00:31:25 CET

On 2/15/07, Roy Franz <roy.lists@gmail.com> wrote:
> As someone who is looking forward to built-in merge tracking support,
> I think having the technical means to control which client versions
> can commit to the repository is very important. Without it, it will be very
> easy for someone to accidentally use an out of date client, and this could go
> unnoticed for some time. While this could be repaired after the fact,
> I would much rather be able to take steps to prevent that. Without
> being able to enforce
> proper client versions the built-in merge tracking loses much of it's appeal, as
> this is a recipe for having incomplete merge information.
> I won't try to make another analogy about the tags dir, but in my environment
> all tags would be suspect until verified if we didn't have a pre-commit hook.
> Not being able to do similar things to protect the merge information would be
> a big loss.
>
> Roy
>
>

We almost never enforce client versions, but rather, client functionality.
We have provisions to negotiate client functionality in both the http
and svn protocols.
We already do it with svndiff1 support.
There is no reason we can't do it with merge-tracking support and
enable one to deny clients that don't report merge-tracking
capability.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 17 00:31:44 2007

This is an archived mail posted to the Subversion Dev mailing list.