samba - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2008-09-16	Use single copy of socket_wrapper in Samba 3 and Samba 4.	Jelmer Vernooij	1	-22/+0

2008-06-10	Revert "Add configure test for vdeplug library."	Stefan Metzmacher	1	-7/+0
	This reverts commit 89590d7dfe0735093a4a5b66eeed9276df043ac9. We don't need this yet and currently config.m4 is also used by samba3 which bail out with the check in it, as it doesn't know about the SMB_EXT_LIB() macro metze (This used to be commit bd0ec1754e6e187d421a718410ecd7c21922aa8b)
2008-02-19	Add configure test for vdeplug library.	Jelmer Vernooij	1	-0/+7
	(This used to be commit 89590d7dfe0735093a4a5b66eeed9276df043ac9)
2007-10-10	r22367: prepare merge to samba3	Stefan Metzmacher	1	-0/+4
	metze (This used to be commit 8da55d6a64925f55f313c928d0441ff607ab3c07)
2007-10-10	r21707: Finally merge my (long-living) perlselftest branch.	Jelmer Vernooij	1	-3/+3
	This changes the main selftest code to be in perl rather than in shell script. The selftest script is now no longer a black box but a regular executable that takes --help. This adds the following features: * "make test TESTS=foo" will run only the tests that match the regex "foo" * ability to deal with expected failures. the suite will not warn about tests that fail and are known to fail, but will warn about other failing tests and tests that are succeeding tests but incorrectly marked as failing. * ability to print a summary with all failures at the end of the run It also opens up the way to the following features, which I hope to implement later: * "environments", for example having a complete domains with DCs and domain members in a testenvironment * only set up smbd if necessary (not when running LOCAL tests, for example) * different mktestsetup scripts per target. except for the mktestsetup script, we can use the same infrastructure for samba 3 or windows. (This used to be commit 38f867880beb40c691e9713f854426031310629c)
2007-10-10	r6621: Warn when the user is trying to use socket wrapper	Jelmer Vernooij	1	-0/+3
	while it is not compiled in. (This used to be commit d63086918ba79307089b3992dc7ed8fc8c6d18a8)
2007-10-10	r6617: Let --enable-developer imply --enable-socket-wrapper	Jelmer Vernooij	1	-3/+13
	Add socket-wrapper-enabled test target and use that by default when the socket wrapper was included (This used to be commit d3b0ad8b4b6f8ee80a9c77e1102960d51ced5a5f)
2007-10-10	r6140: - Add configure option for enabling the socket-wrapper library, so it	Jelmer Vernooij	1	-0/+5
	can be enabled on the buildfarm without requiring --enable-developer - Support tcp and udp being used on the same port - FIx some portability issues (should fix the build on some hosts on the buildfarm) - Ignore setting TCP_NODELAY on (semi-)TCP sockets rather then complain about it not being supported (saves us from a couple of error messages for each connection that is opened) (This used to be commit 443fb7853b8d3cb516c442fdc595038544b75738)