From: Petr Baudis <pasky@suse.cz>
To: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
Cc: martin f krafft <madduck@madduck.net>,
git@vger.kernel.org, Jan Holesovsky <kendy@suse.cz>
Subject: Re: [ANNOUNCE] TopGit v0.3
Date: Tue, 23 Sep 2008 15:27:28 +0200 [thread overview]
Message-ID: <20080923132728.GV10360@machine.or.cz> (raw)
In-Reply-To: <1222175590.10363.14.camel@heerbeest>
Hi,
On Tue, Sep 23, 2008 at 03:13:10PM +0200, Jan Nieuwenhuizen wrote:
> On ma, 2008-09-22 at 17:27 +0200, Petr Baudis wrote:
> [about adding and removing topic branch dependencies]
>
> > Do you really expect you will need this kind of functionality often,
> > though?
>
> Yes. This is what people are used to and do now with our patches based
> system. We cannot take away such basic functionality. Also, currently
> it is very easy to do, however, it is quite error prone. That's also
> why using [top]git would be so great.
>
> There are ~300 topic branches. Usually, a combination of most of these
> is used as the master branch. There are a number of scenarios where
> you would want to add/remove some of these topic branches from master.
>
> The most pressing case for this is for packagers making a release.
> Unless we also make their life easier, we can forget about moving to
> [top]git.
I think that would be possible to do, too. ;-) It really depends on
how general your patch tree is - what we can't make to work is just the
most generic case, but e.g. if master is a *leaf* branch nothing else
depends on and it can't get the branch through multiple paths, you can
do the dependency removal rather easily (if it can get through multiple
paths, you can still do it but you might have to deal with big
conflicts).
But if you scenario indeed is totally generic, I'm afraid I don't know
how to make TopGit remove dependencies, except perhaps for the price of
massive complexity and massive slowdown (pretty much redoing all the
history walking etc.). Maybe someone else comes by with a genial
solution...
--
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-23 13:28 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 [this message]
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
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=20080923132728.GV10360@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=janneke-list@xs4all.nl \
--cc=kendy@suse.cz \
--cc=madduck@madduck.net \
/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).