<meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">trunk_20100722_esteban_diega branch and tag are no longer among us :(</span><div>
<font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">I have also deleted guvnor_expressionEditor3_baunax_esteban_20100202 tag</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Best Regards,<br clear="all"></span></font><br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
<br>Esteban Aliverti<br>- Developer @ <a href="http://www.plugtree.com" target="_blank">http://www.plugtree.com </a><br>- Blog @ <a href="http://ilesteban.wordpress.com" target="_blank">http://ilesteban.wordpress.com</a><br>
<br><br><div class="gmail_quote">On Thu, Jan 20, 2011 at 10:03 AM, Geoffrey De Smet <span dir="ltr"><<a href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi guys,<br>
<br>
In the github reference repository<br>
<a href="https://github.com/droolsjbpm/droolsjbpm" target="_blank">https://github.com/droolsjbpm/droolsjbpm</a><br>
we have /release branches/, such as 4.0.x, 5,0.x, 5.1.x, 5.2.0.M1.x, ...<br>
which is fine,<br>
but also topic branches which clutter our reference repository.<br>
<br>
Following the conventions of other projects, we'd like to move all topic<br>
branches out of the github reference repository, by:<br>
<br>
* 1) Removing the topic branch if it has been merged into master<br>
long ago and has become irrelevant<br>
* 2) Keep the topic branch local (if it's short-lived) until it's<br>
merged into master<br>
* 3) Forking the reference repository on github and push your topic<br>
branches there, until it's merged into master<br>
o For example, edson's fork:<br>
<a href="https://github.com/etirelli/droolsjbpm" target="_blank">https://github.com/etirelli/droolsjbpm</a><br>
<br>
Here's a list of the topic branches that we want to get rid of.<br>
If one of them is yours, please read on.<br>
<br>
* Branch_4_0_2_SOA_4_2<br>
* DRLv6<br>
* DROOLS_4_0_2_SOA_4_2_GA<br>
* DroolsChance<br>
* K200<br>
* effective_dated<br>
* guvnor-pre-guided-changes-june-09<br>
* kstam_guvnor_modeshape<br>
* lr_unlinking_20101116<br>
* persistence_refactor<br>
* rete_using_static_methods_aug2009trunk_20100722_esteban_diega<br>
<br>
If 1) applies and it has been merged into master long ago and has become<br>
irrelevant, then just remove it with this command:<br>
$ git push origin :<branchname><br>
For example:<br>
$ git push origin :kstam_guvnor_modeshape<br>
<br>
If 2) or 3) applies, its a bit more difficult, but I'll make a blog in a<br>
few weeks on how to fork and do social coding.<br>
<br>
--<br>
With kind regards,<br>
Geoffrey De Smet<br>
<br>
<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>
</blockquote></div><br></div>