git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bert Wesarg <bert.wesarg@googlemail.com>
To: martin f krafft <madduck@madduck.net>
Cc: git discussion list <git@vger.kernel.org>, Petr Baudis <pasky@ucw.cz>
Subject: Re: Branch dependencies
Date: Tue, 2 Aug 2011 15:06:40 +0200	[thread overview]
Message-ID: <CAKPyHN0kAJ-MVsrXam5NjsOYkta4nsSrZUvKoMSi-FeRUSuLEw@mail.gmail.com> (raw)
In-Reply-To: <20110801121946.GA575@fishbowl.rw.madduck.net>

Hi,

On Mon, Aug 1, 2011 at 14:19, martin f krafft <madduck@madduck.net> wrote:
> Dear list,

while I appreciate, that you dig this topic up. I think you are trying
to solve the wrong problem first. My main problem with the TopGit
approach is, that you can't freely change the dependencies of a topic.
This may be not the most common case in distro development. But in my
eyes more problematic than maintaining the meta data.

Please note, that I'm more than aware the the TopGit approach for
handling the meta data is awful and we need a new way here. My
personal impression is, that the git notes is the best we can have.

For my first mentioned problem, I think a new 'system' needs to be
'rebase' based, not merge based like TopGit.

Bert

  reply	other threads:[~2011-08-02 13:06 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 [this message]
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     ` Branch dependencies Nicolas Sebrecht

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=CAKPyHN0kAJ-MVsrXam5NjsOYkta4nsSrZUvKoMSi-FeRUSuLEw@mail.gmail.com \
    --to=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).