OK, locally I can do whatever. But how am I supposed to get my work up to remote and master? Merge locally and then push?<br><br>10+ years with CM in my organisation have shown us that branched work is best integrated into the main (master) branch by some coordinating CM role. But Drools isn&#39;t being developed according to some standard Development Life Cycle.<br>
<br>-W<br><br><br><div class="gmail_quote">On 3 January 2011 14:38, ge0ffrey <span dir="ltr">&lt;<a href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Imo, topic branches should be local<br>
or remote on a fork.<br>
i dont think we should litter reference with remote topic branches.<br>
it should only have release branches.<br>
look at hibernate on github.<br>
<font color="#888888">--<br>
View this message in context: <a href="http://drools-java-rules-engine.46999.n3.nabble.com/git-branches-origin-username-tp2180410p2184778.html" target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/git-branches-origin-username-tp2180410p2184778.html</a><br>

Sent from the Drools - Dev mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</font></blockquote></div><br>