git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2] tg-graph: print dependency graph like git log  --graph
Date: Thu, 21 May 2009 11:29:35 +0200	[thread overview]
Message-ID: <36ca99e90905210229s3e621a43h1a336d908d44e685@mail.gmail.com> (raw)
In-Reply-To: <20090520115814.GT8212@noris.de>

On Wed, May 20, 2009 at 13:58, Michael Radziej <mir@noris.de> wrote:
> On Wed, May 20, Bert Wesarg wrote:
>
>> > a) graphviz 2.16-3ubuntu2
>> >
>> > mir@mir:topgit (bw/tg-graph-v2)> tg graph
>> > gvpr: "/usr/local/share/topgit/graph.gvpr", line 952: gg_nl_ret +=
>> > graph_output_commit_line();<<<
>> >  -- cannot convert node_t to string
>> Just a note: I have never seen this error on my side.
>
> graphviz is too old on that system. I've updated to 2.20 and it works fine.
Thanks, I will put a note into the message and try a version check in tg-patch.

>
>> Yeah, sorry I hand edited the patch to use printf instead of echo -e.
>>
>> can you edit this line in tg-summary.sh:
>>
>> printf "\t\"%s\" -> \"%s\";\n" "$$name" "$dep"
>>
>> and change it to this (i.e. remove one '$' from '$$name'):
>>
>> printf "\t\"%s\" -> \"%s\";\n" "$name" "$dep"
>
> Did this, and it works now! (Cheeeers!)
>
> I've attach the output from the big repository (well, the ASCII output is
> not very useful, but the graphics obtained by tg graph --graphviz is). I
> don't have an immediate idea how this could be improved, other than by
> options to strip away a part of the dependencies.
>
> Is
>  tg graph <branch-name>
> expected to work? It results in:
Never tried ;-)


>
> mir@mir:otrs-git (master)> tg graph t/noris-followups
> 3e65695427cf1a15e8a8903e4b11f849045d6800
> ccomps: node "t/noris-followups" not found in graph G - ignored
ccomps decomposes a graph into its connected components. I.e. if you
have topics that depends on master and some one next, you get two
graphs. That itslef improves dramaticaly the graph output, because the
two graphs will be printed separatly. The idea behind the [NAME]
argument is to select only this graph which contains this topic.

Bert
>
> (and no further output)
>
>
> Big thanks so far!
>
> Michael
>
> --
> noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
> Tel +49-911-9352-0 - Fax +49-911-9352-100
> http://www.noris.de - The IT-Outsourcing Company
>
> Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk -
> Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
>

      reply	other threads:[~2009-05-21  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  6:45 [TopGit PATCH v2] tg-graph: print dependency graph like git log --graph Bert Wesarg
2009-05-20 10:37 ` Michael Radziej
2009-05-20 10:48   ` Bert Wesarg
2009-05-20 11:58     ` Michael Radziej
2009-05-21  9:29       ` Bert Wesarg [this message]

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=36ca99e90905210229s3e621a43h1a336d908d44e685@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).