I vote for write a comment and tagging it "NOTSURE", when other people look at the commit probably some of then they will read it and check the validity of it and if it's not valid will raise it and probably between us we can fix/improve it.
On Sun, Mar 30, 2014 at 12:22 PM, mobi phil <[email protected]> wrote: > >> Since a few months I've been trying to add comments when I modify >> something. See gfunc_call as of 0.9.26 for instance and now. However there >> is still some place where I'm not sure of all the lines so I prefer not to >> put a comment that are wrong (it's worse than no comment). >> > > That is for sure greatly appreciated by everybody. Though would be pity to > miss the momentum when you > want to write a comment but you are not sure. What about tagging the > comment "NOTSURE". I think a half > true statement often would be of a great help... Though there is also a > certain risk that it would be missleading ;) > > > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
