From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "martin f krafft" <madduck@debian.org>
Cc: "Petr Baudis" <pasky@suse.cz>,
git@vger.kernel.org,
"vcs distro packaging discussion list"
<vcs-pkg-discuss@lists.alioth.debian.org>
Subject: Re: linearising TopGit forests into patch series (was: [ANNOUNCE] TopGit - A different patch queue manager)
Date: Fri, 8 Aug 2008 19:14:49 +0200 [thread overview]
Message-ID: <36ca99e90808081014j2c48a71bgbff3afae90259e74@mail.gmail.com> (raw)
In-Reply-To: <20080808170658.GA16055@lapse.rw.madduck.net>
On Fri, Aug 8, 2008 at 19:06, martin f krafft <madduck@debian.org> wrote:
> also sprach Bert Wesarg <bert.wesarg@googlemail.com> [2008.08.07.1658 -0300]:
>> Should be doable, I think. At least you can get a topological sorted
>> list of the TopGit branches (with git show-branch --topo-order <list
>> of TopGit-branches>). But than it get complicated, because you don't
>> need the diff from branch-base to branch-head, this would only work
>> for a single dependent list of topic branches.
>
> Hm, I am not entirely following. I understand that I can get
> a topological list of branches, but why don't I need the diff from
> branch-base to branch-head?
branch-base is a merge of all dependent branches, and if there are
more than one you need probably other diffs to get to this merged
branch, than the simple base..head of these branches.
>
> Also, what happens if branches cross-merge?
next prev parent reply other threads:[~2008-08-08 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 3:14 [ANNOUNCE] TopGit - A different patch queue manager Petr Baudis
2008-08-03 7:27 ` Miklos Vajna
2008-08-03 12:02 ` Petr Baudis
2008-08-03 14:14 ` [PATCH] [TopGit] Check for pre-commit hook existence Russell Steicke
2008-08-03 14:26 ` Petr Baudis
2008-08-03 14:45 ` [ANNOUNCE] TopGit - A different patch queue manager Jon Smirl
2008-08-04 13:22 ` Karl Hasselström
2008-08-07 17:56 ` linearising TopGit forests into patch series (was: [ANNOUNCE] TopGit - A different patch queue manager) martin f krafft
2008-08-07 19:58 ` Bert Wesarg
2008-08-08 17:06 ` martin f krafft
2008-08-08 17:14 ` Bert Wesarg [this message]
2008-08-09 1:08 ` Petr Baudis
2008-08-10 20:54 ` Petr Baudis
2008-08-09 2:09 ` Sam Vilain
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=36ca99e90808081014j2c48a71bgbff3afae90259e74@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=madduck@debian.org \
--cc=pasky@suse.cz \
--cc=vcs-pkg-discuss@lists.alioth.debian.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).