Re: Branch dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The 02/08/11, martin f krafft wrote:
> also sprach Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx> [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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]