Mechiel Lukkien 5c33640aea consistently use log.Check for logging errors that "should not happen", don't influence application flow ... sooner or later, someone will notice one of these messages, which will lead us to a bug.		2023-02-16 13:22:00 +01:00
..
atreader.go	mox!	2023-01-30 14:27:06 +01:00
bufpool.go	mox!	2023-01-30 14:27:06 +01:00
bufpool_test.go	mox!	2023-01-30 14:27:06 +01:00
doc.go	mox!	2023-01-30 14:27:06 +01:00
isclosed.go	mox!	2023-01-30 14:27:06 +01:00
limitatreader.go	mox!	2023-01-30 14:27:06 +01:00
limitreader.go	mox!	2023-01-30 14:27:06 +01:00
prefixconn.go	mox!	2023-01-30 14:27:06 +01:00
storagespace.go	mox!	2023-01-30 14:27:06 +01:00
syncdir.go	consistently use log.Check for logging errors that "should not happen", don't influence application flow	2023-02-16 13:22:00 +01:00
trace.go	add two new log levels for tracing sensitive auth protocol messages, and bulk data messages	2023-02-03 20:33:19 +01:00
umask.go	mox!	2023-01-30 14:27:06 +01:00