From: Bert Wesarg <bert.wesarg@googlemail.com>
To: Michael Radziej <mir@noris.de>
Cc: Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org, martin f krafft <madduck@debian.org>,
Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
Adam Simpkins <adam@adamsimpkins.net>
Subject: Re: [TopGit PATCH] tg-graph: print dependency graph like git log --graph
Date: Tue, 19 May 2009 18:45:10 +0200 [thread overview]
Message-ID: <36ca99e90905190945m1ecea6bka99946783ea1d22a@mail.gmail.com> (raw)
In-Reply-To: <36ca99e90905190732g53599cb8y142a137bc79ad655@mail.gmail.com>
On Tue, May 19, 2009 at 16:32, Bert Wesarg <bert.wesarg@googlemail.com> wrote:
> On Tue, May 19, 2009 at 16:14, Bert Wesarg <bert.wesarg@googlemail.com> wrote:
>> On Tue, May 19, 2009 at 16:09, Michael Radziej <mir@noris.de> wrote:
>>> I see another issue. On a quite complicated repository, I did the "tg
>>> summary --graphviz ... edit ... graphviz ..." dance, and there I get the
>>> following output:
>>>
>>> mir@mir:otrs-git$ cat /tmp/graph | gvpr -f ~/src/topgit/share/graph.gvpr
>>> gvpr: "/home/mir/src/topgit/share/graph.gvpr", line 936: gg_nl_ret +=
>>> graph_output_commit_line();<<<
>>> -- cannot convert node_t to string
>> Ok, still two unrelated problems.
> And still I can't reproduce it here :(
I found a missing rename which causes random segfaults.
Here the diff:
--- a/share/graph.gvpr
+++ b/share/graph.gvpr
@@ -523,7 +523,7 @@ BEGIN {
* print the branch lines as "|".
*/
if (gg_prev_state == GRAPH_POST_MERGE &&
- gg_prev_commit_index < gg_opcl_i)
+ gg_prev_n_index < gg_opcl_i)
gg_opcl_sb += gg_write_column(gg_columns[gg_opcl_i], "\\");
else
gg_opcl_sb += gg_write_column(gg_columns[gg_opcl_i], "|");
patch tomorrow
Bert
next prev parent reply other threads:[~2009-05-19 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 5:44 [TopGit PATCH] tg-graph: print dependency graph like git log --graph Bert Wesarg
2009-05-19 10:27 ` Michael Radziej
2009-05-19 10:37 ` Bert Wesarg
2009-05-19 11:08 ` Michael Radziej
2009-05-19 11:47 ` Bert Wesarg
2009-05-19 11:48 ` Bert Wesarg
2009-05-19 13:10 ` Michael Radziej
2009-05-19 13:32 ` Bert Wesarg
2009-05-19 13:39 ` Michael Radziej
2009-05-19 13:51 ` Bert Wesarg
2009-05-19 14:09 ` Michael Radziej
2009-05-19 14:14 ` Bert Wesarg
2009-05-19 14:32 ` Bert Wesarg
2009-05-19 16:45 ` Bert Wesarg [this message]
2009-05-19 13:28 ` martin f krafft
2009-05-19 13:33 ` Bert Wesarg
2009-05-19 18:44 ` Uwe Kleine-König
2009-05-20 6:07 ` 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=36ca99e90905190945m1ecea6bka99946783ea1d22a@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=madduck@debian.org \
--cc=mir@noris.de \
--cc=pasky@suse.cz \
--cc=u.kleine-koenig@pengutronix.de \
/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).