Question/idea about multiple developers committing to one branch

[Nicholas Allen]

Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nicholas Allen wrote:
>   
>> What I think would be cool is if the smart server could enforce that all
>> commits coming into it are through bound branches or checkouts.
>>     
>
> I can see why that has some merit.  There's no way of knowing whether a
> commit is coming from a checkout or not, though.
>
> I think it would be simpler to enforce just the rule that no one can
> change the revision ordering.
You mean that the server could enforce this rule? If it achieves the 
same thing then that's just an implementation detail isn't it? When 
there is an error due to revision history change then the smart server 
could explain to the developer that they should make sure they are using 
a checkout to commit (as this will ensure this). Then the developer 
would create a checkout, merge their original branch into it, and then 
commit from the checkout. Does the server have a means to display error 
messages to the user so it could offer this kind of advice? This would 
also be needed for commit hooks that verify the commits are valid and 
perhaps this could be implemented using a smart server commit hook?

Nick