2012/6/29 <alexdeucher@xxxxxxxxx>: > From: Alex Deucher <alexander.deucher@xxxxxxx> > > This is something I've been wanting to do for a while and > I finally spent a little time getting a start on it. There > is still a lot to do and not all of my descriptions are great, > but I think we can document the rest in bits and pieces. I > also added a note about what asics the function is applicable > to. I tried to start with the more common and complex code. > I was thinking it would make sense to have an informal > documentation policy something like the following: > 1. If you edit an undocumented function, add documentation > 2. If you edit a documented function and change how it works, > update the documentation > 3. All new functions added should be documented > > Fulfulling all of these for stable fixes could pose problems > so obviously there is some leeway. > > Thoughts? I'd try to avoid repeating definitions over and over, but generally THIS IS GREAT. Thanks a lot for doing that! -- Rafał _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
