[Bf-committers] Experimented developer: how are you organised?

Brecht Van Lommel brechtvanlommel at pandora.be
Mon Dec 23 15:45:36 CET 2013


There are some basic commands for that workflow here, but you can
probably find better tutorials online somewhere:
http://wiki.blender.org/index.php/Dev:Doc/Tools/Patches#Creating_Patches_from_Local_Git_Branches

On Mon, Dec 23, 2013 at 9:59 AM, Joshua Leung <aligorith at gmail.com> wrote:
> For each feature you work on, do the development in a new branch, branched
> off master.
>
> When you need to create an updated patch, firstly make sure that you've
> done "git rebase master" (unless you've pushed this branch to some publicly
> visible repo, in which case you'll want to use merge instead) to get your
> branch back in sync with master. Then, do a diff between your branch and
> master, to get the changes your patch does.
>
>
> On Mon, Dec 23, 2013 at 9:39 PM, geof kgeo <kgeogeo at hotmail.com> wrote:
>
>> Why it's only on  one line? Sorry maybe I've missed something.
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list