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

Age	Commit message (Collapse)	Author	Files	Lines
2007-10-10	r8895: work around broken glibc strrchr function that gives valgrind errors ↵	Andrew Tridgell	1	-0/+2
	on some boxes (This used to be commit 5079fdea1b4fde4f844713f42e678759324d801d)
2007-10-10	r5298: - got rid of pstring.h from includes.h. This at least makes it a bit	Andrew Tridgell	1	-0/+2
	less likely that anyone will use pstring for new code - got rid of winbind_client.h from includes.h. This one triggered a huge change, as winbind_client.h was including system/filesys.h and defining the old uint32 and uint16 types, as well as its own pstring and fstring. (This used to be commit 9db6c79e902ec538108d6b7d3324039aabe1704f)
2007-10-10	r5296: - only include the tdb headers where they are needed	Andrew Tridgell	1	-0/+1
	- removed the u32 hack in events.c as I think this was only needed as tdb.h defines u32. Metze, can you check that this hack is indeed no longer needed on your suse system? (This used to be commit 6f79432fe656164d4770dbce114a30dda5e7bf9a)
2007-10-10	r3699: - split the delayed write testing out of RAW-WRITE, as it is not yet	Andrew Tridgell	1	-5/+1
	clear what the correct behaviour is for delayed stat info update. - use a common torture_setup_dir() function for setting up a test directory in torture tests. (This used to be commit f7fb34715b7d6ea3c35ddd684cfb27459a420339)
2007-10-10	r3324: made the smbtorture code completely warning free	Andrew Tridgell	1	-2/+2
	(This used to be commit 7067bb9b52223cafa28470f264f0b60646a07a01)
2007-10-10	r1654: rename cli_ -> smbcli_	Stefan Metzmacher	1	-22/+22
	rename CLI_ -> SMBCLI_ metze (This used to be commit 8441750fd9427dd6fe477f27e603821b4026f038)
2007-10-10	r962: convert 'unsigned' and 'unsigned int' to uint_t	Stefan Metzmacher	1	-3/+3
	metze (This used to be commit 57151e80eb1090281401930c8fe25b20a8cf3a38)
2004-03-26	- moved some of the base tests into torture/basic/	Andrew Tridgell	1	-0/+205
	- added a CHARSET set of tests, which determines how the server deals with some specific charset issues related to UTF-16 support. Interestingly, Samba3 already passes all but one of these tests, because our incorrect UCS-2 and UTF-8 implementations where we don't check the validity of characters actually matches what Windows does! This means that adding UTF-16 support to Samba is going to be _much_ easier than we expected. (This used to be commit c8497a42364d186f08102224d5062d176ee81f5b)