[SCM] SAMBA-CTDB repository - annotated tag 3.6.0-ctdb-22 created - 3.6.0-ctdb-22

[Michael Adam]

The annotated tag, 3.6.0-ctdb-22 has been created
        at  2e9cae14ed6d6247fa060bffd0fa72163845e060 (tag)
   tagging  55c4bb13d605f10e48ae9b44dd1dd27d25c1b9bd (commit)
  replaces  3.6.0-ctdb-21
 tagged by  Michael Adam
        on  Fri Sep 2 14:18:23 2011 +0200

- Log -----------------------------------------------------------------
tag version  3.6.0-ctdb-22
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk5gyZwACgkQyU9JOBhPkDQvCgCeOJ+i3aJB/gBjPx8iDepJgTt4
4j8AnRFgeKH7/WIPvSrf7k256yttZ3PM
=QOvc
-----END PGP SIGNATURE-----

Christian Ambach (2):
      s3:winbindd fix a return code check
      v3-6-ctdb: bump vendor level to 22

Gregor Beck (7):
      s3:net: check return value of check_ctx_create()
      s3:net: registry check handle INFO records
      s3:net: registry check ignore __db_sequence_number__ records
      s3:doc manpage for "net registry check"
      s3:net fix commandline help of "net registry check"
      s3:net let "net registry check" be a little more verbose
      s3:smbcontrol: let smbd pass the idmap msg to its children for convenience

Michael Adam (5):
      s3:registry: fix broken use of dbwrap store record in v1_to_v2 upgrade code
      s3:registry: hand db context in to v2_to_v3 upgrade code via private_data
      s3:registry: define a constant REGDB_VERSION_KEYNAME for the key INFO/version (and use it)
      s3:registry: fix the v1_to_v2 upgrade code so that it does not normalize the INFO/version key ...
      s3:registry: fix the v2_to_v3 upgrade code so that it does not create value list security records for the INFO/version key ...

-----------------------------------------------------------------------


-- 
SAMBA-CTDB repository