From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org, martin f krafft <madduck@debian.org>
Subject: Re: [TopGit PATCH] tg-tred: Print the transitive reduction of the dependecies
Date: Wed, 25 Mar 2009 11:58:41 +0100 [thread overview]
Message-ID: <20090325105841.GB27803@pengutronix.de> (raw)
In-Reply-To: <1237977341-32173-1-git-send-email-bert.wesarg@googlemail.com>
Hello,
On Wed, Mar 25, 2009 at 11:35:41AM +0100, Bert Wesarg wrote:
> +$tg summary --graphviz |
> + tred |
> + gvpr -a "\"${name}\"" '
> +BEG_G {
> + node_t ctr;
> + edge_t e;
> +
> + ctr = isNode($, ARGV[0]);
> + for (e = fstedge(ctr); e; e = nxtedge(e,ctr)) {
> + if (e.head.name != ARGV[0])
> + printf("%s\n", e.head.name);
> + }
> + exit(0);
> +}
I don't know tred and gvpr, just looked shortly over the manpages.
Anyhow what I consider important is that the order of .topdeps is
stable. That is
t/topic1
master
t/topic2
must not be rewritten to
t/topic2
t/topic1
if master is redundant. Is this asserted?
Moreover I wonder if the gvpr program could be optimized when E is used
instead of BEG_G, but as I said above, I don't know how gvpr works.
And note that I intend to change the semantic of tg summary s.t. it only
recurses on the current branch instead of all branches. I think this
doesn't hurt here, though.
Best regards and thanks for your contribution,
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-03-25 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 10:35 [TopGit PATCH] tg-tred: Print the transitive reduction of the dependecies Bert Wesarg
2009-03-25 10:58 ` Uwe Kleine-König [this message]
2009-03-25 11:20 ` Bert Wesarg
2009-03-25 11:24 ` Bert Wesarg
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=20090325105841.GB27803@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=madduck@debian.org \
--cc=pasky@suse.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).