Karl Fogel wrote:
> Blair Zajac <blair_at_orcaware.com> writes:
>> If we're concerned about people using pre 1.5 clients, then we should
>> update the collab.net start-commit to check for the mergeinfo
>> capability.
>>
>> Unfortunately, we can't check for capabilities in the pre-commit
>> script, so you couldn't check that capability only for paths on
>> branches/, so people could still use < 1.5 on trunk.
>
> Two questions:
>
> 1. In the future, should we add a capabilities check in pre-commit?
> (I haven't thought deeply about what's involved in doing that, but
> hey, we could at least get newer clients and servers doing it
> reliably -- the rest is a compatibility dance).
>
> 2. I don't quite understand your last paragraph. How is whether or
> not we can check a capability related to which paths the user is
> committing on? Could you say it more verbosely, maybe?
Well, this shouldn't be an issue for long, but we have a class of committers who
don't have 1.5. For example, my Ubuntu Dapper Drake server has svn 1.3 on it.
It would be nice if you are working on trunk and not doing merges, then you can
use any svn client to commit. However, if you're working on the 1.5.x branch,
then we should require a 1.5 client.
So you could have a pre-commit that checks the paths being commited with the txn
and then checks the capabilities if the path being committed should always have
mergeinfo.
Right now, it's an all or nothing approach with the entire repository.
This wouldn't work with reintegrate merges into trunk, but hopefully people
doing that would know to use a 1.5 client.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-02 05:27:12 CEST