Piotr Krukowiecki <piotr.krukowiecki@xxxxxxxxx> writes: > My suggestions - put each category in their own dir/name space: > > - sources - developer related files you can hack > > - technical/developer documentation like format descriptions, > coding guidelines etc. > > - end user documentation like command documentation, howtos, faqs etc Mild nak. We are talking about a source tree; there is no end-user documentation. Only the sources to it. > - build result - objects, final binaries, generated documentation etc > The advantage besides unclutterting is possibility to have sources on > read-only medium. This is somewhere between a meh to mild nak. "git grep" knows to ignore untracked cruft, so this does not help nor hinder "finding" at all. Even though I personally tend to value seeing frotz.o sitting immediately next to frotz.c, some people may value read-only source tree more than that. -- 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