<p dir="ltr">Hi,</p>
<p dir="ltr">You are trying to 'rebase' instead of 'merge'. Look it up the difference, what you want is to 'merge'.</p>
<p dir="ltr">Rebase is only used for the final patch before committing it to master.</p>
<p dir="ltr">Regards,<br>
Dalai</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Jul 25, 2016 04:34, Pascal Schön <<a href="mailto:pascal_schoen@gmx.net">pascal_schoen@gmx.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Verdana;font-size:12.0px"><div>Hi,</div>
<div> </div>
<div>I've got one question on merging the master branch into the cycles_disney_brdf branch. I'd like to have the current implementation of the multiple scattering GGX in the Disney BSDF. ;-)</div>
<div>But here's the thing: If I do it like it is described here <a href="https://wiki.blender.org/index.php/Dev:Doc/Tools/Git" target="_blank">https://wiki.blender.org/index.php/Dev:Doc/Tools/Git</a>, all of the commits in cycles_disney_brdf will be placed above the commits of the master branch (because of the rebase). But then every commit (also those that have already been pushed before) is published via the mailing list. Or am I wrong here? </div>
<div> </div>
<div>What is the best practise to do this?</div>
<div> </div>
<div>Pascal</div></div></div>
<br>_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-cycles" rel="noreferrer" target="_blank">https://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
<br></blockquote></div></div>