[Bf-committers] Re: [Bf-blender-cvs] Re: CVS commit: blender/source/blender/blenkernel BKE_node.h blender/source/blender/blenkernel/intern ipo.c node.c node_composite.c blender/source/blender/makesdna DNA_camera_types.h DNA_node_types.h blender/s

[Alfredo de Greef]

Thanks! I appreciate that you take the time to reply
anyway...
I'm still not quite clear how this relates to
contributions which were not committed by me
(actually, the yafray code is an example of that as
well) but I think it is best to just assume nothing
really changes then ;)

Alfredo

--- Tom M <letterrip at gmail.com> wrote:

> > Well, the problem is that I don't know what that
> > really means...
> 
> It means that stuff you have ownership of (ie yafray
> code) you can
> commit directly without review by other coders.  If
> you are working on
> someone elses code area generally post a patch to
> the tracker and ask
> them to look over it - and if they say it is okay go
> ahead and commit.
>  Although if there are changes they want they may
> either make them
> themselves and commit or ask you to make the changes
> before
> committing.  Usually it also fine to commit small
> feature additions
> and fixes to other peoples owned modules (basically
> ask yourself if
> you were them would you mind such a commit to code
> you were
> maintaining without a review).  Also if there is
> some area you plan to
> do a lot of work in you can ask ton and the module
> owner to become a
> module maintainer for that area.
> 
> LetterRip
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
>
http://projects.blender.org/mailman/listinfo/bf-committers
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com