Johannes Schindelin, Wed, Aug 29, 2007 16:56:32 +0200: > > > > Your company has certain rules on how all the source on the public > > > > branches should look like, etc. It's not quite clear to me how can > > > > build system enforce these rules. > > > > > > The same as a hook. You just put the check into the Makefile. > > > > How exactly does the Makefile affect what does and what does not get > > checked in? > > By refusing to compile when something's not right? > How do I "compile" that pile of .docs which they called "project documentation"? I really do feel for people working for corporate projects: the rules are strict (and often stupid) and there are mistakes and punishment for them. You really don't want to make a merge of a branch containing commits where description is in wrong format (or wrong content, because the customer may see it, and one of the greate rules of bussiness seem to be "hide and obscure"). People prefer to avoid mistakes from happening, then having to correct them (and yes, they do and will commit without doing sanity check). So I think Pasky has a valid point - 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
