commit 2ca3a24bea4fd072a7e0f83180161516afd47305
from: Stefan Sperling <stsp@stsp.name>
date: Mon Apr 02 12:46:57 2018 UTC

we will probably be using imsg_flush() rather than imsg_compose()

commit - 1e4880cbfee9d652ec24606387f69819c96da4e2
commit + 2ca3a24bea4fd072a7e0f83180161516afd47305
blob - e4d4cb98585281191f6cfe184696e2b55449afd3
blob + dc24c06eec92e79a9617c02e9ef2458ce7123753
--- lib/got_lib_privsep.h
+++ lib/got_lib_privsep.h
@@ -17,7 +17,7 @@
 /*
  * All code runs under the same UID but sensitive code paths are
  * run in a separate process with tighter pledge(2) promises.
- * Data is communicated between processes via imsg_read(3)/imsg_compose(3).
+ * Data is communicated between processes via imsg_flush(3) and imsg_read(3).
  * This behaviour is transparent to users of the library.
  *
  * We generally transmit data in imsg buffers, split across several messages