Re: Branch dependencies

From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date: Aug 4, 2011, 17:38 UTC
Message-ID: <20110804173838.GA10298@vidovic.ultras.lan>
In-Reply-To: <20110802190806.GA16674@fishbowl.rw.madduck.net>

The 02/08/11, martin f krafft wrote:

> also sprach Bert Wesarg <bert.wesarg@googlemail.com> [2011.08.02.1506 +0200]:

> > For my first mentioned problem, I think a new 'system' needs to be
> > 'rebase' based, not merge based like TopGit.
> 
> The problem with rebasing is that you cannot publish the branches.

But you may make public the way to set up the builded branch. Say you share A and B branches and you build M branch on top of them. You are able to build M as long as others know M rely on A and B.

In a situation like

      a--+       (A)
         M--y--z (M)
      b--+       (B)

or

   a--+          (A)
      b--+       (B)
         M--y--z (M)

M is the builded branch. Commits y and z should not be public, IMHO.

-- 
Nicolas Sebrecht