From: "Jens Müller" <blog@tessarakt.de>
To: git@vger.kernel.org
Subject: Re: How to hierarchically merge from the root to the leaf of a branch tree? (Patch stack management)
Date: Fri, 02 Aug 2013 21:18:11 +0200 [thread overview]
Message-ID: <kth0lc$48q$1@ger.gmane.org> (raw)
In-Reply-To: <ktfcq1$v8a$1@ger.gmane.org>
Am 02.08.2013 06:33, schrieb Jens Müller:
> Am 01.08.2013 09:28, schrieb Jakub Narebski:
>> > There is also TopGit, which is feature-branch management tools (which
>> > seems like what you want, from what you written below).
> Indeed, thank you very much for pointing me to it. I have not read the
> whole documentation, but it sounds promising enough that I will try it
> out with some real patches I have flying around and need to combine and
> do further development on.
Seems nice until now, but lacks some essential functionality ... For
example, you can add a dependency to a parent branch, but not remove it ...
prev parent reply other threads:[~2013-08-02 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 22:25 How to hierarchically merge from the root to the leaf of a branch tree? (Patch stack management) Jens Müller
2013-07-31 22:50 ` Fredrik Gustafsson
2013-08-01 7:28 ` Jakub Narebski
2013-08-02 4:33 ` Jens Müller
2013-08-02 19:18 ` Jens Müller [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='kth0lc$48q$1@ger.gmane.org' \
--to=blog@tessarakt.de \
--cc=git@vger.kernel.org \
/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).