From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: martin f krafft <madduck@madduck.net>
Cc: Bert Wesarg <bert.wesarg@googlemail.com>,
git discussion list <git@vger.kernel.org>,
Petr Baudis <pasky@ucw.cz>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Branch dependencies
Date: Thu, 4 Aug 2011 19:38:39 +0200 [thread overview]
Message-ID: <20110804173838.GA10298@vidovic.ultras.lan> (raw)
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
prev parent reply other threads:[~2011-08-04 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:19 Branch dependencies martin f krafft
2011-08-02 13:06 ` Bert Wesarg
2011-08-02 19:08 ` martin f krafft
2011-08-02 23:25 ` Bert Wesarg
2011-08-03 9:51 ` changing the set of dependencies (was: Branch dependencies) martin f krafft
2011-08-03 10:01 ` TopGit with rebased branches, problems with publishing " martin f krafft
2011-08-03 10:10 ` Tracking topic branches with rebases vs. merges " martin f krafft
2011-08-04 17:38 ` Nicolas Sebrecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110804173838.GA10298@vidovic.ultras.lan \
--to=nicolas.s.dev@gmx.fr \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pasky@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).