The intent is for stable branches to remain. If there&#39;s something special I need to do in the retirement prices to guarantee this works, I&#39;d appreciate a pointer in the right direction. So far the myriad of interdependent patches required across all the different repos involved has been a bit confusing, so all help is welcome.<div><br></div><div>    --Adam<br><br><div class="gmail_quote"><div dir="ltr">On Sat, May 11, 2019, 03:51 Andreas Jaeger &lt;<a href="mailto:aj@suse.com">aj@suse.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are you going to retire the complete repo with all branches including<br>
the maintained ones? That means no bug fixes can merge for these anymore,<br>
<br>
Andreas<br>
-- <br>
 Andreas Jaeger aj@{<a href="http://suse.com" rel="noreferrer" target="_blank">suse.com</a>,<a href="http://opensuse.org" rel="noreferrer" target="_blank">opensuse.org</a>} Twitter: jaegerandi<br>
  SUSE LINUX GmbH, <a href="https://maps.google.com/?q=Maxfeldstr.+5,+90409+N%C3%BCrnberg,+Germany&amp;entry=gmail&amp;source=g">Maxfeldstr. 5, 90409 Nürnberg, Germany</a><br>
   GF: Felix Imendörffer, Mary Higgins, Sri Rasiah<br>
       HRB 21284 (AG Nürnberg)<br>
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126<br>
<br>
</blockquote></div></div>