Jelmer,

this is needed since we don't have implemented the functional level change trigger yet (which would also adjust the second value after the first change). The tool should support both the actual unchecked s4 behaviour and the Windows one - therefore this strange-looking exception handling.

Greets,
Matthias

Jelmer Vernooij wrote:
Hi Matthias,

hOn Fri, 2010-05-14 at 12:12 -0500, Matthias Dieter Wallnöfer wrote:
The branch, master has been updated
        via  d712356... s4:repl_meta_data LDB module - fix counter types
        via  8608eae... s4:net domainlevel tool - fix up the error handling as 
Jelmer suggested
        via  6d95a20... s4:dsdb_cache LDB module - fix a typo
        via  da5cd4b... s4:samldb LDB module - remove unused variables
       from  b5dc394... s4:gensec expose gensec_set_target_principal for use 
outside GENSEC

http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit d7123565698fefd16e7696c0e4bb4ec98f6f62ac
Author: Matthias Dieter Wallnöfer<m...@samba.org>
Date:   Fri May 14 18:56:51 2010 +0200

     s4:repl_meta_data LDB module - fix counter types

commit 8608eaef76631666a41109317d2a9b20979c5025
Author: Matthias Dieter Wallnöfer<m...@samba.org>
Date:   Fri May 14 18:59:36 2010 +0200

     s4:net domainlevel tool - fix up the error handling as Jelmer suggested

     Sorry, I've copied this from the "ldap.py" test and thought it would work.
Thanks for fixing that.

Have you verified that we actually need that code? is there a particular
reason why those modifies would fail and if they do should we really
ignore that silently?

Cheers,

Jelmer

Reply via email to