> > I think we should just have one xfree() macro instead of two (xfree and > > xfree_null, some parts of the code even use free() directly). > > I was looking into such things yesterday. Maybe we can write git hooks to > prevent known bad coding conventions from being pushed into the repository > in the future? > > I already have a few sanity checks for Wget in my pre-commit hook. Such > things can be restyled for a server side update hook too.
That sounds very interesting. Please post (or send me private) one or two examples. Tim
signature.asc
Description: This is a digitally signed message part.
