<br><div><span class="gmail_quote">On 6/13/06, <b class="gmail_sendername">Oleg Broytmann</b> <<a href="mailto:phd@oper.phd.pp.ru">phd@oper.phd.pp.ru</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Jun 12, 2006 at 11:31:14PM +0200, Thomas Wouters wrote:<br>> First of all, changing SCM means changing how everyone works.<br><br> Distributed branches is not the only requirement. </blockquote><div><br>Oh, I know, no worries about that.
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">There are also:<br><br>-- subtree authorization (different access rights in different parts of the
<br> tree); in distributed SCMs this is solved by policies, not by tools, as<br> far as I understand;</blockquote><div><br>Pretty much a no-brainer in most SCMs, yes: you need privileges to push certain changes to a repository, not to commit them locally. The receiving repository can make as complicated an authentication and authorization step as it wants. Monotone's approach to this is particularly enjoyable: it works with digital signatures, and you can (have to) tell Monotone who's checkins *you* trust ;)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">-- web-based access (ViewCV or like);</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-- tracker integration (like Subversion with Trac);<br>-- mail notification.</blockquote><div><br>All of these are of course requirements before Python can switch to another SCM, but not for looking at them in the first place -- in most cases, it's not hard to add, if they don't have it already. And besides, while svn has trac integration, we don't actually use it (yet).
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Slightly offtopic: I am working for a company where developers work in<br>different OS (Linux, w32, FreeBSD) and speak different languages (Russian,
<br>Latvian and English). Two features I really love in Subversion:<br>svn:mime-type and svn:eol-style. The former allows to set character<br>encoding for a file (useful for web-based access); the latter allow SVN to<br>automatically convert line endings between different OSes, but it also
<br>allow to set a fixed line ending style for specific files. I don't know<br>another SCM that supports such useful features.</blockquote><div><br>Those two I actually consider more important features than the three you mentioned above -- as they aren't as easily bolted-on. Thanks, I'll keep them in mind :)
<br></div></div><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!