From: Petr Baudis <pasky@ucw.cz>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] TopGit v0.3
Date: Fri, 12 Sep 2008 12:58:39 +0200 [thread overview]
Message-ID: <20080912105839.GV10360@machine.or.cz> (raw)
In-Reply-To: <20080911054030.GA6602@glandium.org>
Hi,
On Thu, Sep 11, 2008 at 07:40:30AM +0200, Mike Hommey wrote:
> I just saw Martin Krafft's talk at debconf 8, showing TopGit, and I
> wonder why TopGit needs to keep top-bases/* references ? Isn't
> git merge-base enough for this ?
the top-bases/ references are to determine what to base the patch
against. Consider patch structure like:
.---- A ----.
vanilla < > C
`---- B ----'
Then, top-bases/C will consist of branches A and B, merging updates in
these branches over time, and you can get the current image of C's patch
by diffing top-bases/C and heads/C. There is no way how to get this by
using git merge-base, since that gives you only kind of "multi-way
diff" - I'm not even sure what would you call merge-base on in this
example.
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
next prev parent reply other threads:[~2008-09-12 10:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 23:10 [ANNOUNCE] TopGit v0.3 Petr Baudis
2008-09-10 8:18 ` Bert Wesarg
2008-09-12 11:01 ` Petr Baudis
2008-09-11 8:03 ` Jan Nieuwenhuizen
2008-09-12 11:00 ` Petr Baudis
2008-09-12 12:27 ` Jan Nieuwenhuizen
2008-09-12 13:15 ` Petr Baudis
2008-09-12 18:14 ` martin f krafft
2008-09-17 10:48 ` Jan Nieuwenhuizen
2008-09-21 14:24 ` Petr Baudis
2008-09-22 9:13 ` Jan Nieuwenhuizen
2008-09-22 15:27 ` Petr Baudis
2008-09-23 13:13 ` Jan Nieuwenhuizen
2008-09-23 13:27 ` Petr Baudis
2008-09-29 10:53 ` Jan Nieuwenhuizen
2008-10-03 10:00 ` Jan Holesovsky
[not found] ` <20080911054030.GA6602@glandium.org>
2008-09-12 10:58 ` Petr Baudis [this message]
2008-09-15 8:01 ` Michael Radziej
2008-09-17 10:11 ` Petr Baudis
2008-09-17 11:17 ` Michael Radziej
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=20080912105839.GV10360@machine.or.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).