X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=NfbUVkj4PAWTTf+zS/Sjq97y57i5P7N4Jj3J84FU6xQ=;
        b=B4xN2vuvmwZmbeAgythj2A7ZCFnyO8vODjUvo3h3eEWzrD5K6SNfnzG90ZUPyt5zjY
         oMIqxWX5oAEWsEg/SjzF8lyMoDTqSYhcjb8osIjyWfp4EoHbocTJ4FMBHyGhWTQxmigj
         bFbt1TrRHJmE3WMMz865JtkyLzPNmsKK68H/qQ9XP65hyvgauoflfrI//XgYM2krOB6v
         QS2eVmUaOf2CPQ0ycondVBpWo/PcS7x2lDic6naiQgHU+6PtdPtG48h8CIjeZN2kTzcz
         Vjaxh3+IQ31h5lRsMh+IDc2yFdUxsBR9QjlHuoFyP1ZC6dmkgySIqtp9/Zd+ko9YkG7o
         xq9A==
MIME-Version: 1.0
Date: Tue, 20 Nov 2012 11:24:56 +0100
Message-ID: <CACwWb3DJsO8J_zAfcSLK=_4iviZy05ZiKj1TFMUUSA8nxO5TwA@mail.gmail.com>
Subject: [geda-user] branches
From: Levente <leventelist AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=14dae93a13bf3edb8304ceeaa528
Reply-To: geda-user AT delorie DOT com

--14dae93a13bf3edb8304ceeaa528
Content-Type: text/plain; charset=ISO-8859-1

I have some slightly off topic question.


How the branches are treated? If we make some commit to the stable-1.8 will
it ever be merged to the master? When do we fork a new branch? If we make a
change to the master, how they going to go to the stable-x.y branch?

--14dae93a13bf3edb8304ceeaa528
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I have some slightly off topic question.<br><br><br>How the branches are tr=
eated? If we make some commit to the stable-1.8 will it ever be merged to t=
he master? When do we fork a new branch? If we make a change to the master,=
 how they going to go to the stable-x.y branch?<br>

--14dae93a13bf3edb8304ceeaa528--