Yann Dirson wrote: > * better API documentation (was previously lacking or plain obsolete) Thanks! In general I find it is easiest to read and write documentation out of line for this sort of thing. That way, even after the documentation grows obsolete it doesn't seem so out of place. See Documentation/technical/api-strbuf.txt, api-sigchain, and api-allocation-growing for some nice (up-to-date) examples. In particular: > * This API is very verbose, and I'm not happy with that aspect. Could you give a quick stripped-down usage example? [...] > Adding "simple" API variants that would call all the necessary stuff > would help code readability, but adding yet more entry points seems a > dubious approach. On the contrary, simple API variants don't sound so bad to me, once the fundamentals are in good shape. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html