I agree that posting a comment about the nature of your commit is important, because documentation is important. Plus there's the educational angle.
On 5/1/07, Josephblack <[EMAIL PROTECTED]> wrote:
On 29/04/07, Petter Urkedal <[EMAIL PROTECTED]> wrote: > On 2007-04-29, Josephblack wrote: snip (thanks to Timothy for writing it): > > http://wiki.duskglow.com/tiki-index.php?page=Subversion+Commit+Policy > > We could always benefit from reviewing it. More eyes and that <g> > > So.. suggestions welcome. > > Looks good to me, snip I like it. I do have a small query about this comment: If you yourself are committing the patch to subversion, then it is not necessary for you to sign your submission on the mailing list. For legal clarity, as long as it is not a minor patch, perhaps all patches should be posted? *all can see there was a change *new ones following can learn why it changed and improve their skills. I have been following the git list, and sometimes a comment about why a fix is needed has been very educational. jb _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
-- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
