On Wednesday 19 of October 2011 14:35:54 Remigiusz Modrzejewski wrote: > On Oct 19, 2011, at 2:18 PM, Richard Hipp wrote: > > I have two suggestion on fossil:**** > > > > (1) support LDAP. It is a essential function for a large enterprise to > > manage users login and authentication.**** > > > > (2) support lock command, http://veracity-scm.org has this command.**** > > My $0.02: both seem to be pretty valid points...
My EUR 0.02: locking creates surprising roadblock once the team grows larger (say, >16 developers, or >8 when distributed geographically). At prev workplace, locks placed carelessly by colleauges from remote offices caused us to miss some deadlines. Of course, it was possible to work 'em around, but it took good understaing of VCS & left some mess in revision history. Why does Veracity tout explicit support for file renames? From what I've seen in Git, the implicit rename model is much more robust -- it does not depend on human factor -- on remembering to issue the right command when moving files around. -- dexen deVries [[[↓][→]]] http://xkcd.com/732/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
